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
I think the private key layout is something like
4 bytes = length data
data = type of key : ssh-rsa or ecdsa-sha2-nistpXXX or ssh-ed25519
depending on type of key repeat until EOF
4 bytes = length data
data
Is this correct ?
I was just looking in the file layout and if I can make a sshkey recognizable that it is encrypted or not.
So you could do that by making an uppercase for the 1st letter of the type of a key and only encrypt the data parts of the file.
The text was updated successfully, but these errors were encountered:
I'd be inclined to OpenSSH format for private keys, see #209 (comment)
If extending Dropbear's format otherwise my inclination would be to add a fixed identifer at the start (and a version field!), then encrypt the current key as-is after that.
Just a question;
I think the private key layout is something like
4 bytes = length data
data = type of key : ssh-rsa or ecdsa-sha2-nistpXXX or ssh-ed25519
depending on type of key repeat until EOF
4 bytes = length data
data
Is this correct ?
I was just looking in the file layout and if I can make a sshkey recognizable that it is encrypted or not.
So you could do that by making an uppercase for the 1st letter of the type of a key and only encrypt the data parts of the file.
The text was updated successfully, but these errors were encountered: