See PHI135. In that case, a user uploaded an SSH private key to passphrase which was missing a header and footer. This (a) didn't work and (b) appeared to be a passphrase key.
We could do a better job of trying to detect invalid private keys (missing header, passphrase-encrypted).
| Restricted Differential Revision | ||
| Restricted Differential Revision | Restricted Diffusion Commit | |
| Restricted Differential Revision | Restricted Diffusion Commit |
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T13454 Handle password-protected SSH keys with no "ENCRYPTED" text in the key body | ||
| Resolved | epriestley | T13006 Passphrase can't distinguish between correct, mangled, and passphrase-encoded SSH keys |
I've marked D20905 as resolving this. This isn't really "resolved" completely, but T13454 has a better description of what the problems are and why they're difficult. Our behavior is, at least, substantially better than it was before.