Pikkola SSH, tool No. 61
Four files stand between you and a server.
The config names the hosts, a key pair proves who you are, authorized_keys holds the public half, and sshd_config decides what the server accepts. This page builds the first, makes a test copy of the second, and reads the fourth before you trust a machine you have not seen.
- 4
- benches
- 0
- uploads
- 700 / 600
- folder, key
The studio
Four benches, four files
Each bench answers on its own, and nothing moves between them unless you copy it. What you paste is read in this tab and what you ask for is made in this tab.
Write ~/.ssh/config, one host at a time
Add a host, fill the fields, and its block appears below in the order ssh reads it. The Host * block is written last and only when you ask for it, because a broad rule at the top would win over the hosts under it.
No host yet. Add one and the file starts.
The name you type after ssh.
The address it connects to. Empty means the name above.
The account on the server.
22 is the default and stays out of the file.
The private key on this machine.
Another host in this file to go through first.
Lets the server use the agent on this machine.
Pick a host on the left to edit it.
ServerAliveInterval 60, AddKeysToAgent yes and IdentitiesOnly yes, at the end of the file so the hosts above keep their own settings.
Save it as ~/.ssh/config, then chmod 600 it.
The four lines that install a key
Four answers, four commands. The comment is only a label on the key, so put there a name you will still recognise in a year.
The server needs sshd running and your key in authorized_keys. If the copy command asks for a password, it is the one you already use on that account.
-
1 Make the pair
The private half stays on this machine. -a 100 makes each passphrase guess slower, which is what protects a file that leaks.
-
2 Copy the public half
ssh-copy-id appends the .pub line to authorized_keys on the server and fixes the folder permissions on the way.
-
3 Lock the files
ssh refuses a private key that others can read. 700 on the folder, 600 on the private key, 644 on the public one.
-
4 Try the login
accept-new records the host key on the first connection and stops if it changes later, which is the part that matters.
Generate a test key in the browser
The browser's crypto makes the pair, the page writes it the way OpenSSH does, and the fingerprint is the SHA-256 of the public blob. Nothing is sent and nothing is stored.
Every key made here lives in this tab. A reload loses it, and that is the point: it is for trying a server, a script or a fingerprint, not for guarding a machine you care about.
This is the line that goes into authorized_keys on the server.
For a test server. On a machine that matters, run ssh-keygen there, or keep the key on a hardware key.
Read an sshd_config before you trust it
Paste the server's file. Each setting is read once and the first value wins, and every line after Match applies only to connections that match it. The page names the lines that open the server wider than it needs to be.
Not in the file
These are the values the server falls back to when a setting is absent. A default is not an opinion, and often not the one you would choose.
The four files
What each file does
Each one is read by a different program at a different moment. Knowing which file is talking is most of the work of fixing a login.
- 1~/.ssh/config belongs to the clientssh reads it top to bottom and the first block that matches the name wins each setting. A Host * at the top therefore wins over every host under it.
- 2Host is the name you type, HostName is where it goesThe two can differ, and usually should. A short name in the file lets an address change without changing what your hands type.
- 3IdentityFile names the private keyssh refuses a private key that the group or others can read, which is why the folder is 700 and the key is 600.
- 4authorized_keys holds the public halfOne key per line, the type first, then the base64 blob, then an optional comment. The file is 600 and the folder 700, or sshd ignores it under StrictModes.
- 5sshd_config belongs to the serverIt is read at start or reload and the first value of a setting wins. A line after Match applies only to connections that match it.
- 6A key in authorized_keys is a way inWhoever holds the private half can use it until that line is removed. Taking away a person's access means editing the file, not changing their password.
Questions
Does anything I paste leave the page?
No. There is no endpoint to send it to, and the page sets connect-src to none, which forbids fetch, WebSocket, beacon and the rest. Load it once and it keeps working with the network off.
Can I use a key this page generated on a real server?
On a test machine, yes. For a machine that matters, make the key with ssh-keygen on that machine or keep it on a hardware key. A private key drawn in a browser has been through more places than one made offline.
ed25519, RSA or ECDSA?
ed25519 unless something is old. It is small, fast and supported everywhere current. RSA 4096 is for servers that predate it, and ECDSA works but brings nothing extra here.
Why does my new host block not apply?
Because an earlier block already matched, and ssh takes the first value it finds. Put the specific blocks above the wildcard. A config with the wrong owner or a readable private key is skipped without a word.
What should I fix first in sshd_config?
PasswordAuthentication no, PermitRootLogin no and PermitEmptyPasswords no, after a key is proven to work. Change one line, reload, and keep the session you have open until a new one gets in.
Does the audit change my server?
No. It reads the text you paste and nothing else. There is no login, no address and no connection, and the file never leaves the tab.