Description
Currently, the client exposes its available auth mechanisms by just listing their types, with no further information. Instead, it could provide supplemental info such as the key sequence number that signed its token, and the fingerprint of the CA cert that signed its certificate. The server could then know not to try negotiating a mechanism that is known to fail (and instead fall back to GSSAPI, for example).