All blog posts
Updates 3 min read

MLS Group Messaging Added to Secure Net Rust

The Rust implementation added a Messaging Layer Security group profile with hybrid post-quantum cryptography using OpenMLS.

By Comutability Published Update from
Smartphone displaying a protected message and shield, representing encrypted MLS group messaging.

Project update: 15 November 2026. GitHub change #12: merged into the repository. The underlying protocol remains draft and unaudited.

The Rust implementation added a Messaging Layer Security group profile with hybrid post-quantum cryptography using OpenMLS.

Why we made this change

Group encryption must cope with membership changes and compromised devices without quietly leaving old keys accessible. This update uses the MLS approach to establish shared group state, while documenting a custom ciphersuite integration that warrants particularly careful expert review.

The engineering record

The original pull request records the following technical scope and evidence. Some forward-looking notes in the record reflect the state of the work when the request was opened, rather than its status today.

Ports Secure Net's MLS group profile (CVP-022) to Rust on OpenMLS, behind groups.* operations, and gives the Rust social client groups. With this, the whole protocol has a Rust implementation.

The OpenMLS patch

OpenMLS has every primitive of MLS_256_XWING_AES256GCM_SHA512_MLDSA87 (X-Wing with HPKE id 0x647a, AES-256-GCM, HKDF-SHA512, ML-DSA-87) but doesn't list that combination, which has no IANA code point yet. rust/vendor/openmls_traits and rust/vendor/openmls_rust_crypto are the crates.io releases with that one suite added under ts-mls's code point (0x0057), wired in with [patch.crates-io]. No cryptography was written. Search for the suite's name to see every changed line. The MIT licence is kept. Drop the copies once the suite is assigned upstream.

Checks

  • test/rust-groups-interop.test.mjs (both CI interop runs): groups that mix OpenMLS and ts-mls devices, in four layouts, with either side committing. Removals, refreshes, replacements and newcomers lock out exactly the right people. Both sides refuse commits and proposals from non-committers, unverifiable key packages, replayed, bent and junk messages, and MLS groups that aren't Secure Net groups. The credential check gives the same answers.
  • tests/groups.rs, tests/groups_e2e.rs (posting through two sites with the reference client) and tests/groups_guards.rs.
  • Mutation check: 21 guards removed in turn, 20 caught. The survivor, the explicit key package suite check, is backed by OpenMLS's own check.
  • WebAssembly: enables OpenMLS's js feature (clock and randomness) and getrandom 0.2's js switch. I couldn't build wasm locally, so CI is the first real build.

Known difference

Saved group states are each library's own (OpenMLS's key-value store in Rust, ts-mls's encoding in JavaScript), so a device keeps the implementation it joined with. Everything on the wire is shared.

This needs human cryptographic review before anyone relies on it.

The wider direction

The Comutability approach is open source with human accountability. AI can help research, design, write code and test it, but a merged change is not the same thing as an independently audited product. Secure Net is explicitly described as a draft in its public README. Its use in a sensitive situation should wait for qualified cryptographic review.

What happens next

Seek independent review of the MLS ciphersuite and group transitions before presenting the feature as production-grade privacy protection.

Read the original sources

Sources and further reading

Explore the evidence and original project records behind this article.