-
Notifications
You must be signed in to change notification settings - Fork 184
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
task: map keys to identities and trust #75
Comments
this issue is linked to GUAC Identity and Trust Problem design doc |
The linked doc is locked to view-only, was that intentional? |
@abuishgair can you make the doc comment access for all? |
I just did. |
mrizzi
pushed a commit
to mrizzi/guac
that referenced
this issue
Jun 21, 2024
…ck-migration deprecated-base-image-check migration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Identities should be considered separate from any given key material, as its potentially a many to many situation. One identity might have multiple keys and one key might be potentially associated with multiple identities.
Note: Identity in this context is still abstract. It should not be tied back to a specific person especially anonymous/pseudonymous folks. The primary goal is to associate keys identities associated with a project, most likely organizations or known maintainers.
Docs:
The text was updated successfully, but these errors were encountered: