5 ms·
Email is a wheel that needs reinventing. It's fundamentally difficult/impossible to secure.
by smt88 6y ago
Email is a wheel that needs reinventing. It's fundamentally difficult/impossible to secure.
- ognarb 6y agoMaybe we need email over the matrix protocol. Decentralized and using an already existing modern open protocol. The problem is that email has too much inertia.
- Jarwain 6y agoWell there's the Matrix Email Bridge: https://matrix.org/docs/projects/bridge/matrix-email-bridge https://matrix.org/docs/projects/bridge/matrix-email-bridge
- Triv888 6y agoThe data of emails is very easy to secure, but the metadata is another story... for example, your email could consist of a single gpg file.
- buster 6y agoWhy do you think that? What would yet another protocol nobody uses bring to the table, smtp and imap don't? It's reliable, stable, decentralized and can be used securely.
- ajvs 6y agoIt's really hard to do E2EE in a user-friendly way with email for starters.
- buster 6y agoThat's what the app does and simplifies.
- smt88 6y agoEmail is not decentralized. It relies on the central authority of domain registries. You theoretically can send emails in a more P2P way by using IP addresses, but then you lose the "reliable" and "stable" parts for many users. It arguably can't be used securely. One of the prominent security researchers on HN actually wrote an article that promising E2EE for email is more harmful than helpful because it gives a false sense of security. And then if you do decide that whatever encryption scheme you've chosen is right for you, there's no guarantee any significant mass of people supports it. In short, email security is a bolt-on, and it will never be part of the standard itself. https://www.csoonline.com/article/3224410/is-universal-end-to-end-encrypted-email-possible-or-even-desirable.html https://www.csoonline.com/article/3224410/is-universal-end-t...
- dane-pgp 6y ago> Email is not decentralized. It relies on the central authority of domain registries. By that definition, almost every chat app is centralized, especially if you include the step of downloading it over HTTPS. In any case, it would be possible to further enhance email using something like SMTorP so that .onion addresses are used instead.[0] > And then if you do decide that whatever encryption scheme you've chosen is right for you, there's no guarantee any significant mass of people supports it. The same is true of any system which is proposed as an alternative to email. Admittedly it will be difficult for a UI to convey the security properties of messages when you are interacting with users whose email clients don't support the recommended extensions, but there is always the risk that a recipient will copy-paste the plaintext of your securely sent message into an unsecured channel. [0] https://github.com/mailpile/Mailpile/wiki/SMTorP https://github.com/mailpile/Mailpile/wiki/SMTorP
- smt88 6y ago> By that definition, almost every chat app is centralized, especially if you include the step of downloading it over HTTPS. That analogy makes no sense. Email is centralized because every time I send an email, I'm doing a DNS lookup. By contrast, if I use a true P2P solution, I never need to do a DNS lookup. My chats in Signal can't be disrupted by a change in MX records. > In any case, it would be possible to further enhance email using something like SMTorP so that .onion addresses are used instead. Yes, but then why are you using email at all? The whole point of email has been that it uses the domain registry as a routing mechanism. It's like telling people that the WWW is decentralized as long as you use .onion addresses. That's not true because as soon as you get off of public domains, you're not on the WWW anymore. > The same is true of any system which is proposed as an alternative to email. I don't think you understand this topic. There are protocols with encryption schemes built into them. Email is not one of those. From the article I linked: > "A number of standards exist for end-to-end email encryption, but so far, none have reached critical mass with vendors. Take Symantec. It supports both the S/MIME and PGP/MIME encryption, says Symantec's Kriese. That doesn't mean that the system easily interoperates with those of other vendors." That is in contrast to Signal Protocol[1], where all clients' E2EE are compatible with each other as long as they're using the same protocol. 1. https://en.wikipedia.org/wiki/Signal_Protocol https://en.wikipedia.org/wiki/Signal_Protocol
- gsich 6y agoSee Deltachat.
- hkt 6y agoMetadata being available to the server isn't ideal, but a hub and spoke architecture where the hub has no knowledge of which spokes are talking is, if not impossible, then at least very hard, surely? On the other hand, TLS by default would be nice
- spicybright 6y agoI feel like the first step is consistent encryption, then figuring out hiding meta data. Proxys that strip meta + delay emails to fuzz that might be a solution.
- dane-pgp 6y agoAgreed. In fact, if consistent E2E encryption could be assumed, then the proxies could be implemented as simply a dedicated address on each server. For example, suppose alice@example wants to send an encrypted message to bob@server. Alice's client could wrap the message to Bob as an encrypted payload to a message addressed to switchboard@server, so that her provider doesn't learn Bob's address, and her provider could replace her metadata with switchboard@example before sending it to Bob's, so that it doesn't learn Alice's address.