-
Notifications
You must be signed in to change notification settings - Fork 27
Address Crypto Panel review comments #330
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
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.
Looks good Vasilis. See separate comments for nits.
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Addressed the comments! Thank you 🙏 |
draft-irtf-cfrg-bbs-signatures.md
Outdated
@@ -601,7 +608,7 @@ Furthermore, all core operations accept the Signer's public key (`PK`) as well a | |||
|
|||
### CoreSign | |||
|
|||
This operation computes a deterministic signature from a secret key (`SK`), a set of `generators` (points of G1) and optionally a `header` and a vector of `messages`. | |||
This operation computes a deterministic signature from a secret key (`SK`), a set of `generators` (points of G1) and optionally a `header` and a vector of `messages`. Note that signature generation is deterministic, in contrast to the academic literature, where signature generation, and more specifically the calculation of the `e` value (Procedure step 2 below), is randomized (i.e., the `e` value is drawn at random, instead of been deterministically calculated by hashing the Signer's secret key and the list of messages). This alteration not only protects the scheme (at least the signature generation part) from vulnerabilities related to bad entropy sources, it also makes testing of the `CoreSign` operation easier. |
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.
Note that signature generation is deterministic, in contrast to the academic literature
Maybe we should reference Revisiting BBS Signatures here where they suggest it may have better security properties?
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.
Looks good with Andrew's fixes too.
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Co-authored-by: Andrew Whitehead <[email protected]>
Editorial updates to address the CFRG Crypto Panel review: https://mailarchive.ietf.org/arch/msg/crypto-panel/Vk5O4h_U3-QcWrm22KWwRFmSl7E/