News for hackers. Stuff that matters.
Re:What every IT person needs to know about OpenBSD Part 3: ... by matja on Saturday November 20, 2021 @07:56PM (#29293200)
An SSH password is sent to the server, the server will get the exact password. An SSH private key is not sent to the server.
Re:What every IT person needs to know about OpenBSD Part 3: ... by GekkePrutser on Saturday November 20, 2021 @08:11PM (#29293296)
Exactly, so even if the server is compromised you're not giving it the means to authenticate as you. I think this is a huge plus.
Re:What every IT person needs to know about OpenBSD Part 3: ... by valenterry on Sunday November 21, 2021 @04:54AM (#29295215)
Maybe, but it conceptually it doesn't have to be like that. Often, the password is not sent directly, but its hash is sent (sometimes hashed multiple times), so that the same property is true.
Re:What every IT person needs to know about OpenBSD Part 3: ... by hnaccount141 on Sunday November 21, 2021 @03:44PM (#29299519)
If you send a hash, the hash itself effectively becomes the password. If the server is compromised or the hash is intercepted, the attacker has everything they need to authenticate as you.

With private/public key pairs, the same scenario would result in the attacker only obtaining your public key, which is useless without the private key.

Re:What every IT person needs to know about OpenBSD Part 3: ... by valenterry on Sunday November 21, 2021 @07:57PM (#29301464)
You are correct and I was sloppy in explaining it properly.

In general however, I believe that there is no inherit advantage of certificates over passwords, except for the key-size obviously. Everything else is just convention/standards.

Please see the following page that explains better what I meant when I said that the password should be hashed: https://en.wikipedia.org/wiki/Hash_chain

Using such a mechanism (including salts / challenges) will prevent an attacker using the hash as the password.