-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add note about deterministic key generation #12
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
draft-bradleylundberg-cfrg-arkg.md
Outdated
### Deterministic key generation | ||
|
||
Although the above definition expresses the key generation as opaque, | ||
likely sampling random key distributions, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
likely sampling uniformly random key distributions,
draft-bradleylundberg-cfrg-arkg.md
Outdated
likely sampling random key distributions, | ||
implementations MAY choose to implement the functions `BL-Generate-Keypair()`, | ||
`KEM-Generate-Keypair()` and `ARKG-Generate-Seed()` | ||
as deriving keys deterministically from some given input key material. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"as deterministic functions for a given input."
ARKG-Generate-Seed()
does not derive a key.
draft-bradleylundberg-cfrg-arkg.md
Outdated
implementations MAY choose to implement the functions `BL-Generate-Keypair()`, | ||
`KEM-Generate-Keypair()` and `ARKG-Generate-Seed()` | ||
as deriving keys deterministically from some given input key material. | ||
This can be thought of as defining a single-use ARKG instance where these functions return a constant result. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"This can be thought of as defining a single-use ARKG instance where these function outputs are static."
(2024-04-03) Review comments from @AltmannPeter and @sander: There are desired use cases for deterministically generated seed keys, such as that outlined in the example here.
I don't think the defined procedures really need to change, since this is rather an implementation detail for the delegating party. I think we can just note that implementations are free to make that choice, without defining an interoperability API for this.
(A formal definition of
ARKG-Generate-Seed
is needed just to tieBL-Generate-Keypair
andKEM-Generate-Keypair
together, but its implementation details are not important for interoperability, unlikeARKG-Derive-Public-Key
andARKG-Derive-Secret-Key
.)