2 ms·
Why would I ever not want the server to require a password, though? Like, if your server ain't asking for a password at all, then why even bother with the keyl
by yellowapple 8y ago
Why would I ever not want the server to require a password, though? Like, if your server ain't asking for a password at all, then why even bother with the keylogger?
- samus 8y agoPostgresql supports authentication via TLS client certificate, which requires no password. Even then, a keylogger might be able to catch other secrets.
- anarazel 8y agoPeer authentication for local postgres servers / poolers (authenticate using the OS users, doesn't work remotely, and yes, it's safe), kerberos / [gs]sspi authentication, client certificates.
- yellowapple 8y agoAh, right, forgot about those options. Still, if you know that you're connecting to a server that's setup with password-based auth, then what would be the point of waiting? You'll inevitably have to provide a password as some point anyway, so the keylogger argument seems silly. And if someone has the ability to install a keylogger on a machine that uses peer or certificate auth, then that someone almost certainly already has the ability to just connect directly using that same peer or certificate auth.