Re: An additional-auth mechanism for SSH to protect against scanning/probing attacks
Peter Gutmann <[email protected]> Fri, 6 Jan 2023 12:12:00 +0000
| Newsgroups | gmane.ietf.secsh |
|---|---|
| Message-ID | <SY4PR01MB6251078A4DC0EF0C67FB1F21EEFB9@SY4PR01MB6251.ausprd01.prod.outlook.com> |
Damien Miller <[email protected]> writes: >fwiw OpenSSH handles lines from the server before the SSH-banner just fine: Ah, yeah, I saw OpenSSH as a server rather than client so never checked that one, but I would have expected it to get this bit right :-). >The SSH banner line is a bit special in that its contents are guaranteed to >be bound into the key exchange hash, Yup, that was a major reason for using it for that. Way too many IETF protocols in the past have ignored channel binding and either had to kludge it in afterwards or just left that aspect vulnerable, so having the non-SSH preauth cryptographically bound into the SSH protocol itself is a design feature. Peter.