SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01reconexisting shares: same name? same folder already shared?
- 02recondoes the folder exist?
- 03recondoes the given account exist? (a SID = yes)
- 04reconSMB1 disabled? encryption enabled?
- 05actCreate the folder (only if missing)verify
- 06actCreate the sharedestructiveverify
- 07actNTFS rights for the accountverify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyCreate the folder (only if missing)Verified by
Test-Path '${path}' - 02verifyCreate the shareVerified by
Get-SmbShareAccess -Name '${name}' | Select-Object AccountName,AccessRight - 03verifyNTFS rights for the accountVerified by
(Get-Acl '${path}').Access | Select-Object IdentityReference,FileSystemRights
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never grant access to "Everyone" or Authenticated Users. Do not remove any existing ACL. Do not enable SMB1. Do not open port 445 to the Internet.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${name} | Share name |
| ${path} | Folder |
| ${account} | Allowed account |
SEC.05
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain SMB file share or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.07
More storage & backup recipes
- 01Swap fileCreates a persistent swap file of the chosen size. Destructive: modifies /etc/fstab.
- 02restic backupsrestic + a scheduled, encrypted backup of a folder to a repository.
- 03MinIOS3-compatible MinIO object storage via Docker, local-only. Community project archived: frozen image.
- 04Garage (S3 storage)Garage (Deuxfleurs) S3-compatible object storage via Docker, single-node and local-only, with a first bucket and its key. Maintained alternative to MinIO.
- 05Samba shareSamba file server (SMB). Destructive: creates a share and a user.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.