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.

Sign up for GitHub

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

Jump to bottom

Should add an API to issue third-party certifications (e.g. over a UserId) #347

Closed
hko-s opened this issue May 7, 2024 · 0 comments · Fixed by #349
Closed

Should add an API to issue third-party certifications (e.g. over a UserId) #347

hko-s opened this issue May 7, 2024 · 0 comments · Fixed by #349

Comments

@hko-s
Copy link
Contributor

hko-s commented May 7, 2024

The function UserId::sign (and similar ones) currently assumes that the signer key is also the key that the UserId should be bound to. This is fine for self-signatures, but doesn't allow third-party signatures.

We should add an API that allows passing in two separate key parameters: a signer and a key to bind (e.g.) the UserId to.

I can propose a PR soonish.

(Cc @kyrias, fyi)
@hko-s hko-s changed the title Should add an API for issue third-party certifications (e.g. over a UserId) Should add an API to issue third-party certifications (e.g. over a UserId) May 7, 2024
@hko-s hko-s mentioned this issue May 10, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add APIs for third-party certifications hko-s/rpgp
1 participant
@hko-s