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. 01reconWindows edition and build (ProductType 1 = workstation, 2 = DC, 3 = server), RAM
2. 02reconOpenSSH Server installed? (preinstalled on Windows Server 2025)
3. 03reconis the sshd service already running?
4. 04reconsshd_config and administrator keys already present? (do not overwrite)
5. 05reconexisting OpenSSH-Server-In-TCP firewall rule? port 22 already taken?
6. 06actInstall OpenSSH Serververify
7. 07actStart + automaticdestructiveverify
8. 08actFirewall ruledestructiveverify
9. 09actRestrict access (only if an allowed IP is provided)verify
10. 10actCheck the config and the portverify

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 OpenSSH ServerVerified by(Get-WindowsCapability -Online -Name OpenSSH.Server*).State
2. 02verifyStart + automaticVerified by(Get-Service sshd).Status
3. 03verifyFirewall ruleVerified by(Get-NetFirewallRule -Name 'OpenSSH-Server-In-TCP').Enabled
4. 04verifyRestrict access (only if an allowed IP is provided)Verified by(Get-NetFirewallRule -Name 'OpenSSH-Server-In-TCP' | Get-NetFirewallAddressFilter).RemoteAddress
5. 05verifyCheck the config and the portVerified by(Test-NetConnection -ComputerName localhost -Port 22 -WarningAction SilentlyContinue).TcpTestSucceeded

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 OpenSSH Server 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 system recipes

1. 01TimezoneSets the server timezone.
2. 02CockpitCockpit web administration console, local-only (SSH tunnel) by default, on :9090.
3. 03Zsh + Oh My ZshZsh with Oh My Zsh for the current user.
4. 04Synchronized clock (chrony)NTP synchronization via chrony.
5. 05User + sudoCreates a user with SSH key and sudo access. Destructive: system account.