earthstar-project / earthstar-project/willowprotocol.org

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

Open
#69 0 comments 0 reactions 1 assignee Claimed by @AljoschaMeyer View on GitHub
Dominant language
TypeScript
Stars
44
Forks
6
Avg merge
1d 21m
Merged PRs (30d)
1

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.