-
Notifications
You must be signed in to change notification settings - Fork 23
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
Delete expired KeyPackage, rotate KeyPackages #541
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! How do we plan to delete the key material from the old key package on the client once the new package is uploaded? Is the idea to pipe an expiry into MLS for the old package at the time that the new one is created?
For the CI issue, just run |
openmls = { git = "https://github.com/Bren2010/openmls", rev = "3992d09" } | ||
openmls_basic_credential = { git = "https://github.com/Bren2010/openmls", rev = "3992d09" } | ||
openmls_rust_crypto = { git = "https://github.com/Bren2010/openmls", rev = "3992d09" } | ||
openmls_traits = { git = "https://github.com/Bren2010/openmls", rev = "3992d09" } | ||
prost = "^0.12" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't a PR be put up against https://github.com/xmtp/openmls with any necessary changes here?
(Rather than changing the base repo on which we're using. )
Without more context here for why this change is necessary, I would advise on holding off on merging this until:
- It's clear here why we should switch to using Brendan's fork, or
- we wait for the changes to land in
xmtp/openmls
and we retain that dependency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a PR here: xmtp/openmls#20
The Cargo.toml here was just changed temporarily
ee291c5
to
85112a0
Compare
My idea was just to just leave all KeyPackages in storage until they expire, based on the thought that they might still be used. |
We still need to rotate the KeyPackage if there haven't been any Welcome messages processed in the last X months, but I'm not sure the best way to implement that check?