SSH collector: diagnosable key rejection, and pastes that actually work
Fixes the failure @tslpre hit in #6, where every SSH source failed with an opaque unable to authenticate, attempted methods [none publickey].
I tested the connector against a real sshd with ed25519, ECDSA, RSA (OpenSSH and PKCS#1) keys, encrypted and not, through the HTTP API — the SSH auth itself is correct, including rsa-sha2 negotiation against servers that disable legacy ssh-rsa. That error only reproduces when the server refuses the key we offered, and Homedex printed nothing about which key that was. That opacity was the real bug.
- Key rejection now tells you how to fix it. The error reports the fingerprint, key type, and the exact
authorized_keysline Homedex offered, plus the account it used. Copy-paste instead of guesswork. - Real-world pastes work. Keys pasted with surrounding blank lines or editor indentation used to fail with
ssh: no key found. PEM is whitespace sensitive and a browser textarea invites both. - Browser autofill no longer breaks a valid key. A value autofilled into the passphrase field is ignored for unencrypted keys.
- Clearer mistakes: pasting a public key, or an encrypted key without its passphrase, now say exactly that.
- Form status messages wrap and keep line breaks, so the new multi-line guidance is readable.
Docs: SSH troubleshooting.