About
Tool No. 61 of Pikkola
An ssh login is decided by four files. One is yours, one is a pair of keys, one sits on the server, and one decides what the server accepts. Three of them are short enough to keep in your head, and the fourth is the one people get wrong, so this page builds the first, makes a test copy of the second, and reads the fourth.
What it does
- Builds a ~/.ssh/config from host cards. Each card writes Host, HostName, User, Port, IdentityFile, ProxyJump and ForwardAgent, in the order ssh reads them.
- Leaves Port 22 out of the file, because it is the default, and leaves a field out when it is empty.
- Writes the optional Host * block at the end, never at the start, and says so where the switch is.
- Copies the config or downloads it as
config. - Generates the four commands that install a key: ssh-keygen, ssh-copy-id, the chmod line and a test login.
- Generates an ECDSA P-256 or RSA-2048 key pair with the browser's WebCrypto, and writes the public half in OpenSSH format and the private half as PKCS#8 PEM, with the SHA-256 fingerprint.
- Reads a pasted sshd_config and names the settings that open a server further than it needs to be.
- Speaks English, Korean and Japanese, follows the light and dark theme, and copies every result.
How the config is assembled
A block is written in a fixed order: Host, then HostName, User, Port, IdentityFile, ProxyJump, ForwardAgent. Fields you leave empty are skipped rather than written as empty, so the file says only what you filled in. Blocks are separated by one blank line and the file ends with a newline.
The order of the blocks is the order of the list, because that order is part of the meaning. For each setting, ssh takes the first block whose Host matches, so a specific host belongs above a wildcard. That is why the Host * block, when you ask for it, is appended at the end.
Nothing else is added: no date, no generated-by comment, no editor setting. What you copy is exactly what the panel shows.
How a key is made
The pair comes from crypto.subtle.generateKey, which is the browser's own implementation of the standard, not a copy of it in the page. ECDSA uses the P-256 curve; RSA uses 2048 bits with a public exponent of 65537.
The public key is rebuilt in the format OpenSSH writes: a length-prefixed type name, the curve name for ECDSA or the modulus and exponent for RSA, each length-prefixed, then base64 on one line with an optional comment. The fingerprint is the SHA-256 of that same blob, base64 encoded without padding, which is what ssh-keygen -lf prints.
The private key is exported as PKCS#8 and wrapped in PEM, which is the BEGIN PRIVATE KEY block. Nothing is uploaded at any step, and the key is held in a variable on the page rather than in storage.
How the audit reads a file
Lines are read the way sshd reads them. A # starts a comment and the rest of the line is dropped. A setting is a keyword and a value. For most keywords sshd keeps the first value it meets and ignores later ones, so a second appearance is reported as a line that does nothing, not as a change.
Everything after a Match line is conditional, and the finding says so, because a setting inside a Match block may not apply to the connection you are worried about. The page does not try to evaluate Match conditions; it shows the line and lets you judge.
The score starts at 100 and loses points for each finding by severity. It is a reading aid, not a measurement: a file with a low score is not necessarily broken, and a file with 100 has not been tested against your version of sshd.
Where the limits are
- No connection. The page never reaches a host, so it cannot tell whether a port is open, a key is installed, or a config on a server is the one you pasted.
- One file. A
~/.ssh/configcan include another file, and sshd_config can useInclude; this page reads what you paste and does not follow either. - Defaults move. The value sshd falls back to when a setting is absent depends on the version and the distribution, so the defaults the page names are the common ones, not a guarantee.
- Keys made here are test keys. They are real key pairs, but a private key that has been drawn in a browser has been through more places than one made offline, and it is gone when the tab reloads.
- The commands are the common form. A server with a non-standard port, a jump host or a different authorised key file needs the flags adjusted, and the page shows the flags so they can be.
- No checking of your server. The audit is a reading of text. Run
sshd -tbefore a reload and keep a session open while you change anything.
Why it is free
Pikkola builds small tools with one job each and keeps them free, with no account and no lock on the result. A page that runs in the browser costs almost nothing to serve, so there is no reason to charge for it or to watch who uses it.
Contact
A setting the audit should know, a command that does not work on your system, a Korean or Japanese sentence that reads badly: hello@pikkola.com. The line you pasted and the sshd or ssh version are the most useful thing to send.