4 ms·
HTTPS is just an encypted pipe. The authentication only works one way (you authenticate the server) and it only involves mapping a string (www.example.com for e
by upofadown 4y ago
HTTPS is just an encypted pipe. The authentication only works one way (you authenticate the server) and it only involves mapping a string (www.example.com for example) to the cryptographic identity through a trusted third party.
Encrypted email embodies an entire encrypted end to end messaging system with authentication of all the users involved in a discussion. The problem is harder and we have not settled on any good usability standard for this. The usability of end to end encrypted messaging is still quite bad for online connected media like instant messaging as well.
- Avamander 4y ago> The problem is harder and we have not settled on any good usability standard for this. Actually the CA/B Forum S/MIME workgroup just recently agreed upon the baseline requirements for future S/MIME certificate issuance. This also means an ACME-like process for mailbox-validated S/MIME certificates is or will be possible in the future. Identity validation is a much more difficult, human problem. Some countries have solved that for their citizens, but due to how shit S/MIME has been so far, encrypted/signed containers have been used (a lot) instead.
- 0x0 4y agoActually, until a few years ago, browsers did support a rarely used feature for client TLS authentication and the <keygen> html tag.