Re: rsa-sha2-256/512: handling of incorrect signature encoding

[Matt Johnston <matt%ucc.asn.au@localhost>]

On Thu, Aug 04, 2016 at 04:04:16AM +0000, Peter Gutmann wrote:
> I was thinking of it in an opportunistic-upgrade sense, for example for PGP
> and S/MIME the mandatory algorithm is SHA-1 but if you receive a message
> signed with SHA-2 you can switch to that because the client will be able to
> process it.  So if you see ecdsa-sha2... or rsa-sha2... in the keyex then you

The pubkey signature could have come from a ssh-agent (only
supporting rsa-sha1) that's elsewhere to the SSH client.

Cheers,
Matt