-
Notifications
You must be signed in to change notification settings - Fork 512
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
WIP: Add a no-op server endpoint for rotating keys, and make the client use it #529
Conversation
err error | ||
) | ||
switch role { | ||
switch s.role { // parseKeyParams ensures it's only timestamp or snapshot |
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.
Note - this logic goes away and GetOrCreateXKey
gets unified in the next PR.
awesome tests, LGTM pending comments! |
Signed-off-by: Ying Li <[email protected]>
This also changes GetKey and RotateKey to return a data.PublicKey, rather than bytes. Signed-off-by: Ying Li <[email protected]>
… rotating keys. Signed-off-by: Ying Li <[email protected]>
Signed-off-by: Ying Li <[email protected]>
5b46db7
to
c04f9a5
Compare
@riyazdf @NathanMcCauley thanks for the quick review! I've just made a new function |
…motely. Signed-off-by: Ying Li <[email protected]>
Marking as WIP due to some discussion on #534 that may change how this works |
Since so much has changed, opening new request #533 instead. |
The PR for the full server rotation of keys was getting a bit big, so here are some cherry-picked parts.
Currently the endpoint always returns a 429 (rate limit).
Part of #347