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.

1. 01reconSamba already installed + version
2. 02reconservice active (smbd on Debian/Ubuntu, smb on RHEL)
3. 03recondoes a share with the same name exist? existing config to preserve
4. 04recondoes the folder exist? current permissions (do not change them)
5. 05reconsystem account and Samba account already present?
6. 06recon445/139 already in use?
7. 07recondistro, SELinux, firewall active
8. 08actInstall Sambaverify
9. 09actCreate the system user (no shell)verify
10. 10actPrepare the shared folderverify
11. 11actGenerated Samba passwordverify
12. 12actAdd the ${share_name} sharedestructiveverify
13. 13actEnable and restart Sambaverify
14. 14actTest the share locallyverify
15. 15actOpen Samba to the local network (only if a firewall is active and asked)verify

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.

1. 01verifyInstall SambaVerified bysmbd --version
2. 02verifyCreate the system user (no shell)Verified byid ${smb_user}
3. 03verifyPrepare the shared folderVerified bystat -c '%U %a' ${share_path}
4. 04verifyGenerated Samba passwordVerified bypdbedit -L | grep -c '^${smb_user}:'
5. 05verifyAdd the ${share_name} shareVerified bytestparm -s 2>/dev/null | grep -c '^\[${share_name}\]'
6. 06verifyEnable and restart SambaVerified bysystemctl is-active smbd 2>/dev/null || systemctl is-active smb
7. 07verifyTest the share locallyVerified byss -tlnH "sport = :445" | wc -l
8. 08verifyOpen Samba to the local network (only if a firewall is active and asked)Verified byufw status 2>/dev/null | grep -ci samba || firewall-cmd --list-services

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

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.

SEC.06

Deploy on Servor button

Maintain Samba 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

1. 01Swap fileCreates a persistent swap file of the chosen size. Destructive: modifies /etc/fstab.
2. 02restic backupsrestic + a scheduled, encrypted backup of a folder to a repository.
3. 03MinIOS3-compatible MinIO object storage via Docker, local-only. Community project archived: frozen image.
4. 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.
5. 05Borg backupsBorgBackup + a scheduled encrypted backup of a folder.