Re: [Curdle] Client-side SSH_MSG_EXT_INFO: Use it or lose it principle!

>> Anyone who can't/won't understand that there is a spec, and it isn't
>> "it interoperates with PuTTY and OpenSSH", deserves, IMO, to be
>> ignored.
> That's fine if you have no responsibility towards your clients/users.
> It doesn't work if you do, [...]

I disagree.  Strongly.

I didn't say that anyone who files a bug report such as you sketch
deserves to be ignored.  It's only the ones who are unable or unwilling
to understand that their "the new piece is the buggy one" (or, perhaps,
"it works with $OTHER implementation, so it's not broken") stance might
actually be wrong - and that there actually is an impartial right and
wrong to it - _those_ are the ones who deserve to be ignored.

And that much only after education efforts have demonstrated
exceptional resistance to acquisition of clue.

As for responsibility?  As an ssh implementor, I hold myself to have a
responsibility to all my users to call brokenness brokenness, rather
than hiding it.  (Yes, moussh has bug and misfeature workarounds
implemented.  None of them are turned on by default, and all of them
are documented as workarounds.)

That responsibility is to the whole ssh ecosystem, actually.

Maybe that's part of why moussh is so unpopular.  So be it; I do _not_
feel I have a responsibility to be popular at the cost of making the
situation even worse.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		[email protected]
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B