MLS protects group messages by making membership changes explicit
Group chat has a key-management problem. A secure messenger can encrypt a message from one device to another, but a group needs every current member to share key material while removing departed members and surviving device changes. Messaging Layer Security, or MLS, defines a protocol for that work. Its useful security lesson is that group membership must become an explicit, verifiable state transition rather than an assumption held by the chat service.
MLS is specified in RFC 9420, published in July 2023. The protocol uses a group context and advances through epochs. A Commit message instructs current members to apply a set of proposals and move to a new epoch. The epoch secret is intended to remain confidential to members of the current epoch. That design gives a client a concrete point at which to change keys after adding or removing a member.
Membership is more than a contact list
Each MLS client publishes a KeyPackage containing an HPKE public key and a credential that describes its identity. A LeafNode in the group tree carries a client's signature key and capabilities. A client that accepts a group must verify the signatures and credentials using application-defined identity rules. MLS can prove that a leaf signed a statement, but the application still has to decide whether that credential belongs to the account it expects.
This distinction matters during recovery and conflicting-device cases. A chat provider may display the same user name for two clients, while the MLS credential identifies different signing keys. If the application treats the provider's contact label as the security identity, a replacement device can appear to be the same member without meeting the application's account-recovery policy. The verifier needs a mapping from the MLS credential to an account identity it trusts.
The membership change also needs application handling. A Commit can add members, remove them, or update their keys. A removed client may still possess ciphertext from earlier epochs. Epoch changes prevent that client from deriving later secrets, but they cannot erase messages or files it already received. Applications that retain long-lived history should state their retention model and avoid treating a key rotation as retroactive deletion.
Operational checks
A receiving client should process commits in order and reject an unexpected epoch transition. It should keep the signature-key and credential checks connected to the account system, including the rules for new devices and recovery. Servers should expose enough group state for clients to detect a stale commit without allowing the server to invent membership silently.
Monitoring should record epoch changes, member additions and removals, and failures to verify a KeyPackage or Commit. The audit record can include opaque group IDs and credential fingerprints, not message plaintext. Multi-device applications also need a policy for clients that remain offline across several epoch changes and for users who lose every trusted device.
MLS replaces improvised group-key distribution with a protocol state machine. The application still owns account proof, authorization, recovery, and history. Those boundaries deserve review before a group secrets change is treated as a security event that clients will actually enforce.
Top comments (0)