-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add recommendation for deletion of init_key
s
#269
base: main
Are you sure you want to change the base?
Conversation
Thinking more about init keys, we should also recommend to regularly rotate key packages that are on the delivery service, even if they are not used. This could otherwise undermine post-compromise security: the attacker could compromise the initialization key of someone, and when the corresponding key package is added in a group later (e.g. several months after the compromise) the attacker can decrypt the messages exchanged in this group, until the participant updates. |
There are some hints that key packages must expire: mls-architecture/draft-ietf-mls-architecture.md Lines 1819 to 1822 in b8893e0
but I think kind of attack undermines post-compromise security rather than forward secrecy. |
I am wondering, should it be a "RECOMMENDATION"? It seems that other "RECOMMENDATION" are about things that can only be done in a best-effort way, whereas deleting initialization key upon Welcome processing seems to always be doable. |
I opened #274 to discuss KeyPackage expiration. |
In WGLC; see this. |
Because the
joiner_secret
is encrypted to theinit_key
of joiners, if the joiners don't delete theirinit_key
after processing a Welcome, this could undermine forward-secrecy. I noticed that the document don't give any precise recommendations about that.There are some hints scattered in the document, but they give recommendations to participants adding other participants, not to participants being added:
mls-architecture/draft-ietf-mls-architecture.md
Lines 670 to 672 in b091b3a
This PR adds a recommendation for that. I am not sure on how to proceed, I have made an attempt but it might belong to another section!