6 ms·
Messaging layer security: Secure and usable end-to-end encryption
- rektide 4y agoCongrats!! Very long time coming & very exciting! Will it get an rfc number soon?
- palata 4y agoI am a bit confused, I only find an abstract there. Is it supposed to link to a longer definition that would become an RFC?
- rektide 4y ago> The IETF has approved publication of Messaging Layer Security (MLS) Dated March 29th. Not quite final, but I believe this link is about the imminent release of the core spec.
- upofadown 4y agoThese are the current drafts: * https://datatracker.ietf.org/group/mls/documents/ https://datatracker.ietf.org/group/mls/documents/ You have to click on the "Document" tab.
- palata 4y agoOh, somehow it was not so clear to me on smartphone. Thanks!
- deleted 4y ago[deleted]
- upofadown 4y agoThis is great an all but it doesn't really address the big problem with end to end encrypted messaging. That would be the usability issue. There is no point in constantly designing new protocols if very few people will ever be able to use the resulting systems. We make these things and then wait for someone to come along and make them usable. That never seems to happen. I think we really have to turn things around the other way. First determine what a usable system would look like and then only after that is determined start thinking about the cryptography that would work for that system. After all, the cryptography aspect seems to be the relatively easy problem. We solve it over and over again.
- palata 4y agoSo that was my question: is this supposed to be some kind of interoperable e2ee? If yes, then that would be some equivalent of TLS but for e2ee, somehow. But then we need a protocol on top of that (for TLS that's HTTPS) to actually have interoperability at the application level, right? But then it feels similar to saying "let's all agree to use the Signal Protocol and write interoperable clients, doesn't it? If I want a slightly different experience that requires a sightly different protocol, then suddenly I cannot interoperate anymore... Or am I missing something?
- kitkat_new 4y agoWhatsApp is used by billions, and uses (at least in theory) e2ee, so I don't think usability is a real problem for e2ee
- upofadown 4y agoSo what percentage of those billions are correctly using the ridiculously long numbers (60 decimal digits) used to represent identities (WhatsApp calls them "security codes") in that system to ensure they are actually communicating end to end? WhatsApp doesn't even inform the user of changes to these numbers by default[1] so my guess would be that practically no WhatsApp users are working end to end. WhatsApp can intercept messages at will. I am not singling out WhatsApp here. In a usability study involving Signal[2], 21 out of 28 computer science students failed to establish and maintain a secure end to end encrypted connection. [1] https://faq.whatsapp.com/1524220618005378 https://faq.whatsapp.com/1524220618005378 [2] https://www.ndss-symposium.org/wp-content/uploads/2018/03/09-when-signal-hits-the-fan-on-the-usability-and-security-of-state-of-the-art-secure-mobile-messaging.pdf https://www.ndss-symposium.org/wp-content/uploads/2018/03/09...
- kitkat_new 4y ago> WhatsApp doesn't even inform the user of changes to these numbers by default[1] is this everything?
- ajconway 4y ago
- palata 4y agoIf that's meant to be an RFC: > Other apps, such as Wickr and Matrix, are planning to transition to MLS [...] Matrix is a protocol, not an app, right? Maybe I'm being pedantic, but I tend to trust RFCs, so... cannot hurt to be precise, I think.
- kitkat_new 4y agodefinitely protocol https://spec.matrix.org/v1.6/ https://spec.matrix.org/v1.6/
- jeroenhd 4y agoMatrix is a protocol that is managed by "The Matrix.org Foundation" (https://matrix.org/foundation/ https://matrix.org/foundation/). If the Matrix Foundation says they're transitioning to MLS, I suppose Matrix as a protocol is also shifting towards interoperability.
- palata 4y agoSure. My point is that if it is a protocol, then the RFC should not say that it is an app :-)
- halJordan 4y agoBut by the same token, you're calling a blog post an rfc. If we're going to be fast and loose with words it should at least be allowed across the board.
- palata 4y agoI said "if that is meant to be an RFC". Of course if it is not meant to be an RFC, then it does not really matter... English is not my mother tongue, so maybe I missed something here.
- regularjack 4y agoAFAICT this is not an RFC, it's just a blog post.
- kitkat_new 4y agoI hope MLS will support a decentralized messaging system, which will be required for interoperable systems with no central authority like the Matrix network. Originally it didn't[0], I hope this has changed or will. Otherwise, I'd guess it would be dead on arrival. [0] https://matrix.uhoreg.ca/mls/decentralised.html https://matrix.uhoreg.ca/mls/decentralised.html
- walterbell 4y agoInteroperability work on top of MLS is underway. Edit: see https://news.ycombinator.com/item?id=35366250 https://news.ycombinator.com/item?id=35366250 for audio. https://datatracker.ietf.org/doc/bofreq-cooper-more-instant-messaging-interoperability/ https://datatracker.ietf.org/doc/bofreq-cooper-more-instant-... & https://news.ycombinator.com/item?id=33420112 https://news.ycombinator.com/item?id=33420112 > The IETF had multiple prior lines of effort in this area during the development and widespread deployment of XMPP and SIP decades ago, but the nature of existing messaging implementations and the external environment have both changed significantly since then. Messaging applications now share more common content features and functionality, the MLS protocol has been developed to facilitate E2EE interoperable messaging, and regulatory pressure to interoperate has increased significantly (e.g., as a result of the EU Digital Markets Act). https://mailarchive.ietf.org/arch/msg/mimi/CI3z3CUPE8rrC5p4_ysJYY7ELD4/ https://mailarchive.ietf.org/arch/msg/mimi/CI3z3CUPE8rrC5p4_... & https://techcrunch.com/2022/12/30/inside-matrix-the-protocol-that-might-finally-make-messaging-apps-interoperable/ https://techcrunch.com/2022/12/30/inside-matrix-the-protocol... > We sometimes found that the various components of Matrix came together in unexpected ways that created problems, even if they were fine in isolation. From our reading of the charter and current drafts, it is likely that MIMI will need to include new cryptographic protocols (or integrate existing ones). As such, an analysis that looks at how the pieces of the puzzle fit together would be valuable. Thus, we'd like to advocate for following the path of MLS and TLS 1.3 by engaging the security, privacy, cryptography and formal verification communities.
- ianopolous 4y agoAs your link discusses, MLS still requires centralization because of the requirements of total ordering of some messages by the delivery service. If you want a truly p2p encrypted group chat protocol then look at DCGKA by Matthew Weidner, Martin Kleppmann et al: https://dl.acm.org/doi/10.1145/3460120.3484542 https://dl.acm.org/doi/10.1145/3460120.3484542
- brongondwana 4y agoThe MIMI working group is meeting at IETF116 in Yokohama RIGHT NOW. I'm sitting in the meeting. There's a live audio stream at https://datatracker.ietf.org/group/mimi/meetings/ https://datatracker.ietf.org/group/mimi/meetings/ or the video will be posted later after the meeting. You can also find links from that page to the charter, mailing list, etc, if you want to get involved.
- kitkat_new 4y ago125$ for 1 day access remote, are they serious? https://registration.ietf.org/116/ https://registration.ietf.org/116/
- brongondwana 4y agoYep, you can apply for a fee waiver if that's a significant challenge, but this org costs quite a lot to run (there's quite a big staff keeping the meeting running). Having said that, the pricing for remote participants is currently a major topic of discussion. https://datatracker.ietf.org/doc/draft-ietf-shmoo-remote-fee/ https://datatracker.ietf.org/doc/draft-ietf-shmoo-remote-fee...
- dwaite 4y agoYep. Organizations cost quite a bit to run (mostly a mix of staff and marketing), and have different models for funding it. Some are more closed in participation, asking organizations and individuals to pay anywhere from $5k to $100k to participate, while some charge for the specs they produce. IETF gets 40% of their revenue from meetings, but has managed to figure out how to fund open participation and open specs.
- warner25 4y agoI know some academics working on MLS and I spent some time last year trying to understand it, to decide if I wanted to work with them. I think this blog post doesn't mention the core problem that MLS is trying to solve, which is efficient and secure key management (including forward secrecy and post-compromise security, which the Signal Double Ratchet protocol does so elegantly) for group end-to-end encrypted messaging. You don't want to have a O(n^2) keys for n users to talk to each other, and you don't want to have a single shared session key that must be renegotiated among all participants every time one participant leaves or gets kicked out of the group. I think MLS can do this with O(lg n) keys and fewer key exchanges as participants come and go.
- skrowl 4y ago[dead]
- tptacek 4y agoI've sort of mentally bucketed MLS into "secure end-to-end messaging for large group applications", like Slack or Telegram, where Signal's idea of a "group" is more akin to a bunch of people making plans to meet up for drinks or something. (I don't know how accurate this really is, and MLS people would also probably argue that their abstractions work nicely for small groups too).
- DJBunnies 4y agoIs that not what schnorr signatures solve?
- tptacek 4y ago... no?
- upofadown 4y ago>I think MLS can do this with O(lg n) keys and fewer key exchanges as participants come and go. Does this potentially help with the group end to end encrypted chat identity problem? The number of identities that need to be verified goes up O(n^2) with the number of participants. It is hard to make that usable.
- issafram 4y agoI love standards so this is great. Someone smarter than me please explain the differences between this and the Signal Protocol.
- warner25 4y agoSee my other comment about this being a way to achieve all the nice properties of the Signal protocol in an efficient and scalable manner for group messaging instead of just 1:1 messaging.
- tptacek 4y agoThe big difference between MLS and Signal Protocol is that MLS is tree structured (it began with a tree key derivation algorithm called ART, and now uses one called TreeKEM). An MLS group is structured as a binary tree with communicants at the leaves; pairs of communicants share an addressable key, as do pairs of pairs (forming subgroups) all the way on to the root, which computes a key that addresses the whole group. Signal Protocol is entirely pairwise. A Signal group is a set of communicants who have established N^2 pairwise ratcheting relationships with each other.
- throw_a_grenade 4y ago> Other apps, such as Wickr and Matrix, are planning to transition to MLS What exacty is the Matrix' plan wrt MLS? This announcement sounds almost like they will retire current Matrix 1.6 protocol. Is this accurate?
- erlend_sh 4y agoMSC3923: Bringing Matrix into the IETF process — https://github.com/matrix-org/matrix-spec-proposals/pull/3923 https://github.com/matrix-org/matrix-spec-proposals/pull/392... MSC3977: Matrix as a Messaging Framework — https://github.com/matrix-org/matrix-spec-proposals/pull/3977 https://github.com/matrix-org/matrix-spec-proposals/pull/397... MSC3919: Matrix Message Format — https://github.com/matrix-org/matrix-spec-proposals/pull/3919 https://github.com/matrix-org/matrix-spec-proposals/pull/391... MSC3918: Matrix Message Transport — https://github.com/matrix-org/matrix-spec-proposals/pull/3918 https://github.com/matrix-org/matrix-spec-proposals/pull/391...
- Arathorn 4y agohttps://arewemlsyet.com https://arewemlsyet.com. We won’t retire the current olm/megolm but complement it with MLS, and perhaps transition entirely if MLS works out.
- tptacek 4y agoMatrix is already really complicated! You'd really consider having it run two interacting ratcheting group messaging protocols?
- anticensor 4y agoThey can peacefully coexist in a room by room choice of algorithm. Your other MIMI proposal, linear Matrix rooms, would weaken the integrity asumptions and completely change the trust model.
- ementally 4y agorelated https://blog.quarkslab.com/secure-messaging-apps-and-group-protocols-part-2.html https://blog.quarkslab.com/secure-messaging-apps-and-group-p...