RE: Feedback on draft-ssh-ext-info-00
Peter Gutmann <[email protected]>
| Newsgroups | gmane.ietf.secsh |
|---|---|
| Message-ID | <9A043F3CF02CD34C8E74AC1594475C73F4B986A0@uxcn10-5.UoA.auckland.ac.nz> |
denis bider <[email protected]> writes: >Presence of "rsa-sha2-256" as a host key signature algorithm cannot reliably >serve as an indicator for user authentication, because it requires the server >to actually have an RSA host key. Ah, OK, I'd missed that. Maybe the -sha2 draft could point this out, I saw section 3 but didn't connect it with the issues of identifying algorithms, since my code does all of them so will just accept something like an ECDSA server sig combined with an RSA client sig. >The server might only have an ECDSA host key; but may still accept and prefer >"rsa-sha2-256" signatures for client authentication. Hmm, which leads to a follow-on question, is this actually going to be an issue? Are there going to be implementations out there that support signature algorithm A in one case but only signature algorithm B in another? Peter.