-
Notifications
You must be signed in to change notification settings - Fork 22
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
Define the agent fingerprint as the SPKI. #301
Conversation
This should address the issues raised in #282, while overall certificate management needs more discussion. |
@baylesj to take a look. |
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.
LGTM % feedback.
@backkem, this PR uses the SPKI as defined in RFC 7469, but thank you for the earlier PR :-) |
@baylesj, PTAL |
Went and merged this as I believe the last comments are addressed. Please let me know if there are additional comments @baylesj |
SHA: ca83371 Reason: push, by mfoltzgoogle Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Addresses Issue #282: Certificates should have a maximum lifetime, and SPAKE2 identities should be SPKI not cert fingerprint
This defines the agent fingerprint in terms of the SPKI (e.g., the public key) of the agent certificate. The agent fingerprint is used to identify agents and is input to SPAKE2.
This allows agents to use shorter-lived certificates and renew their certificates without having to re-authenticate to other agents.
This PR does not specify certificate lifetimes or renewal policies. It also does not handle the issuing of completely new certificates while maintaining previous trust relationships.
Preview | Diff