Now I understand why almost no one uses encrypted email

Re:Now I understand why almost no one uses encrypted email by wuunderbar on Thursday April 16, 2020 @07:56PM (#22894826)

> SSH

Still requires a passphrase or initializing a keypair on the client & server.

> HTTPS

HTTPS requires user interaction when a site forgets to renew a certificate.

Also SSH and HTTPS don't compare well. One does client authentication, the other doesn't.

[ Parent | on HN ]

Re:Now I understand why almost no one uses encrypted email by couchand on Thursday April 16, 2020 @09:36PM (#22895417)

You absolutely can do client authn in HTTPS, but it's rarely done outside intranet apps and high-security banking.

[ Parent | on HN ]

Re:Now I understand why almost no one uses encrypted email by lordlimecat on Friday April 17, 2020 @08:19AM (#22898342)

Your complaint about a login system is about its authentication, in a discussion on encryption and key exchange?

The obvious point being made is that going from SMS -> E2E should be as seamless as from telnet -> ssh.

SMS and messaging systems generally do require some level of authentication so you're making a ridiculous comparison.

[ Parent | on HN ]

Re:Now I understand why almost no one uses encrypted email by de_watcher on Friday April 17, 2020 @08:51AM (#22898533)

auth_pam/auth_basic in the nginx config and the http/https does authentication.

And far less space to mess things up than with coding a fancy login page.

[ Parent | on HN ]