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.

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

Clarify potential number of public keys in use by a Meadowcap user #69

Open
sgwilym opened this issue Feb 19, 2024 · 0 comments
Open

Clarify potential number of public keys in use by a Meadowcap user #69

sgwilym opened this issue Feb 19, 2024 · 0 comments

Comments

@sgwilym
Copy link
Collaborator

sgwilym commented Feb 19, 2024

https://community.spritely.institute/t/meadowcap-capability-system-for-controlling-access-to-willow-data/411/3

By using “her public key” the system makes tracking trivial. In a system that better protects privacy, each capability should be tied to a unique key pair created for just that purpose. I would change that text to say

The implementation relies on signature schemes again. Consider Alfie and Betty, each able to create many key pairs. Alfie can mint a new capability for Betty by signing his own capability together with a public key Betty has created for this purpose…

Meadowcap does not mandate that each user only has one public key, and that is not self-evident from the current text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant