If you have to compare the two, look at the length of your password compared to the length of your private key.

if your ssh server is completely open with no password or key. Diffie Hellman is used by TLS/HTTPS and most other encrypted communication to securely negotiate a shared encryption key over an insecur

In addition if that private key is stored (one way) in a crypto card, e.g. PIV ID card, OpenPGP card, YubiKey, then it can't be exfiltrated by a keylogger or malware even on a compromised PC, though o

(Quote)

One thing that should be mentioned - password-based authentication is vulnerable to hosting-provider database leak (if it was not changed by a client obviously) unlike public key authentication. I con

(Quote)

For protocol 2, forward security is provided through a **Diffie-Hellman key agreement**. This key agreement results in a shared session key. The rest of the session is encrypted using a symmetric ciph

If keys is painful to use for some people so 30-45 characters password is great 😂

(Quote)

Only if you do not understand the term cryptographic strength. SSH keys are not just a "password", it's an asymmetric encryption. To be able to authenticate you have to match the pub

(Quote)

(Quote)

The default ssh key size is 3072 bits. Assuming your password truly is 100% random (and i.e. has 8 bit entropy per character), then a 24 character password has 192 bits of entropy.

Password: something you know

"No matter how long or complex a password is, it can never equate with the cryptographic strength that SSH public key offers."

Assuming a really strong password is used, are keys really more secure than passwords for SSH login?

(Spoiler)

(Quote)

Also the root password in the mail history doesnt work

Both VPS are running cpanel.