Re: How to handle incorrectly-encoded public keys

Peter Gutmann <[email protected]> Sun, 20 Nov 2022 05:45:14 +0000

Newsgroups	gmane.ietf.secsh
Message-ID	<SY4PR01MB625165468D4BF0BFF046B8E9EE0B9@SY4PR01MB6251.ausprd01.prod.outlook.com>

I wrote:

>even the do-everything PuTTY doesn't seem to have any knowledge of this so
>maybe it's obscure enough that nothing has noticed it before.

Just checked the OpenSSH code, that doesn't seem to know about this either, so
it really could be that it's never encountered the real world.

Peter.