You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per OpenSSH's PROTOCOL.key, the two 32-bit checkint fields are immediately followed by privatekey1, "where each private key is encoded using the same rules as used for SSH agent." So we may need to find those rules. The above looks like it's length field followed by ASCII key type id (ssh2 or ecdr), but it's better to know for sure per spec.
For new format OpenSSH private keys, which use bcrypt-pbkdf, we check only 4 bytes. For our 4 test vectors, the decrypted data starts with:
Per OpenSSH's
PROTOCOL.key
, the two 32-bitcheckint
fields are immediately followed byprivatekey1
, "where each private key is encoded using the same rules as used for SSH agent." So we may need to find those rules. The above looks like it's length field followed by ASCII key type id (ssh2
orecdr
), but it's better to know for sure per spec.I also found https://coolaj86.com/articles/the-openssh-private-key-format/ which has some useful info, but is someone else figuring this out rather than an official spec.
The text was updated successfully, but these errors were encountered: