Skip to content

Simon/feat/decrypt targeted message - #2425

Draft
SimonThormeyer wants to merge 17 commits into
simon/feat/targeted-message-message-enumfrom
simon/feat/decrypt-targeted-message
Draft

Simon/feat/decrypt targeted message#2425
SimonThormeyer wants to merge 17 commits into
simon/feat/targeted-message-message-enumfrom
simon/feat/decrypt-targeted-message

Conversation

@SimonThormeyer

Copy link
Copy Markdown
Member

No description provided.

Instead of using an enum type like openmls does, we use a struct, which
implements its own instance (in the future, instances) as constants, as
seen in mls-rs.

This is a pattern that looks cleaner and also has a technical advantage,
it uses less memory, because it doesn't need a discriminant.
We need to map it to our conversation error when signing a core crypto
message payload.
When encrypting targeted messages, we're going to use it if the
recipient client id isn't present in the current epoch.
We need that method to find the encryption key of a client id.
We need to be able to increment the sender nonce in the closure.
@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/decrypt-targeted-message branch 2 times, most recently from b46c530 to 1fb2154 Compare August 3, 2026 14:44
@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/decrypt-targeted-message branch from 1fb2154 to 3ce3db2 Compare August 3, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant