Skip to content
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

triage(Keys_Incoming): Investigate key rotation #6531

Closed
1 task
Tracked by #5606
LHerskind opened this issue May 20, 2024 · 1 comment
Closed
1 task
Tracked by #5606

triage(Keys_Incoming): Investigate key rotation #6531

LHerskind opened this issue May 20, 2024 · 1 comment
Assignees

Comments

@LHerskind
Copy link
Contributor

LHerskind commented May 20, 2024

With key rotation of the incoming key we need to have a more flexible method of decrypting messages that are of interest to use.

As it is not yet fully clear how much is really broken by rotating keys, we need to triage it first. I expect that performing a key-rotation during the token tests is likely to show os most of the issues that we will encounter.

I think the note processor is the main place where we need additional logic to address multiple keys, but it is not clear to me yet.

Please investigate what is broken by rotating, and create issues in here as more is encountered.

Look for "TODO(#6531)" in the codebase.

Tasks

Preview Give feedback
@benesjan
Copy link
Contributor

benesjan commented Aug 9, 2024

Outdated issue now so I am closing it

@benesjan benesjan closed this as completed Aug 9, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants