Re: OpenSSH bug in decoding EXT_INFO extension values
"denis bider \(Bitvise\)" <[email protected]> Fri, 23 Jun 2017 07:18:25 -0600
| Newsgroups | gmane.ietf.secsh |
|---|---|
| Message-ID | <43E5E2A1DD834CDE8432FCA0EBFB32E3@Khan> |
Aye – I thought there’s nothing simpler than: string extension-name string extension-value <= can contain any value! But... there we go. :) It’s fascinating how much non-simplicity one discovers in things that seem simple. *sigh* You know what the most common misunderstanding of our users is? They don’t know what’s a “client” and what’s a “server”. From: Markus Friedl Sent: Friday, June 23, 2017 06:41 To: denis bider (Bitvise) Cc: Damien Miller ; [email protected] Subject: Re: OpenSSH bug in decoding EXT_INFO extension values 2017-06-14 11:43 GMT+02:00 denis bider (Bitvise) <[email protected]>: > And when you do that, I am then peeved if you simultaneously abrogate this > responsibility, by developing, planning, and designing sloppily. Just try to make simpler protocol extensions, so I can keep seeing sloppy -m