<<< confirmation of ssh-userauth starting
>>> request mouse/ssh-connection/none
<<< failure, can-continue publickey,password,keyboard-interactive
>>> request mouse/ssh-connection/keyboard-interactive
<<< failure, can-continue publickey,password,keyboard-interactive
"Yeah, Openssh does that." Openssh does not keep track of whether an
authentication method has failed to be useful on the server side. It
[...] expects the client to deal with this.
Okay, I can live with that (I have to be prepared to do *something* in
the face of arbitrarily broken servers, after all, and it's not that
difficult to keep a list of auth methods that appear to be
misbehaving.)
That answers the question of what openssh means in doing this - it's
rejecting keyboard-interactive auth, just in a way that rather confused
me. But it raises the question of why openssh is rejecting
keyboard-interactive auth at all. Any thoughts on that?