Dropbear not identifying key correctly?

[MarCoMLXXV]

I generated a new ssh key this morning, using PuTTy Key Generator as I previously saw dropbear in syslog warning for using a SHA1 key, allthough I was sure I generated a RSA SHA2 key with ssh-keygen. So I generated a 256 bit ECDSA RSA2 key with passphrase, removed the old key on both server and client side, but still:

May 26 09:33:29 dropbear[17144]: Pubkey auth succeeded for '********' with key sha1!! <fingerprint>

@RMerlin: Any idea why Dropbear still warns for using sha1, while the key is definitely not sha1?

 

[RMerlin]

I generated a new ssh key this morning, using PuTTy Key Generator as I previously saw dropbear in syslog warning for using a SHA1 key, allthough I was sure I generated a RSA SHA2 key with ssh-keygen. So I generated a 256 bit ECDSA RSA2 key with passphrase, removed the old key on both server and client side, but still:

May 26 09:33:29 dropbear[17144]: Pubkey auth succeeded for '********' with key sha1!! <fingerprint>

@RMerlin: Any idea why Dropbear still warns for using sha1, while the key is definitely not sha1?

That's not an error message, that's normal notification. SHA1 is merely a signature used to identify a key, it's not the key itself.

 

[MarCoMLXXV]

That's not an error message, that's normal notification. SHA1 is merely a signature used to identify a key, it's not the key itself.

Ah, I see. I interpreted the exclamation mark as a warning. Strange though it notifies of a SHA1 signature when using a key with a SHA2 signature. I'll try to ignore it, as in I'll try to let my OCD not tokick in when I see the notifcation come by Thanks for the reply.

 

[RMerlin]

Ah, I see. I interpreted the exclamation mark as a warning. Strange though it notifies of a SHA1 signature when using a key with a SHA2 signature. I'll try to ignore it, as in I'll try to let my OCD not tokick in when I see the notifcation come by Thanks for the reply.

Usually, keys are identified by an MD5. That might be why it seems to imply something is unusual, as I disabled MD5 support in dropbear, forcing it to switch to SHA1 for signature report.