guac
guac copied to clipboard
task: map keys to identities and trust
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:
- https://docs.google.com/document/d/1BUEi7q2i-KXlAhsh1adYvL1fkWN-q8FrgLyEre7c5kg/edit?resourcekey=0-02sC5-9IbTfwJckze_CDQw#heading=h.h9kfextfhlqn
- https://docs.google.com/document/d/15xa3HDvV_O7xeh-ahEPjUwdKQGlZmOVDgtsk0f5hqUc/edit?usp=sharing
this issue is linked to GUAC Identity and Trust Problem design doc https://docs.google.com/document/d/15xa3HDvV_O7xeh-ahEPjUwdKQGlZmOVDgtsk0f5hqUc/edit?usp=sharing
The linked doc is locked to view-only, was that intentional?
@abuishgair can you make the doc comment access for all?
I just did.