-
Notifications
You must be signed in to change notification settings - Fork 26
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
Update encoding rules #216
Update encoding rules #216
Conversation
draft-looker-cfrg-bbs-signatures.md
Outdated
7. el_octs = I2OSP(length(el), 8) || el | ||
8. else if el is a Point in G1: el_octs = point_to_octets_g1(el) | ||
9. else if el is a Point in G2: el_octs = point_to_octets_g2(el) | ||
4. if el is an octet string representing a public key: |
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.
Is this used? Why not just pass it as a G2 point?
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.
We definitely could, but i like having the PK as an octet string. It's more intuitive for a developer IMO. Also updating this would be a bigger change (will need to update the octets_to_pubkey
to something like validate_pubkey
which I'm not sure how it would look like. Opened #219 to keep track of this.
aee86e0
to
b6df3ca
Compare
…s-signature into BasileiosKal-encoding_updates
With the CFRG draft adoption the draft name has changed again, please rebase this PR to target the new draft name |
a542045
to
e84c3d9
Compare
Multiple approvals, open over two weeks, merging |
Closes #207
DSTs are defined as octet strings everywhere. Default DSTs are turned into octet strings using
utf8
. Also, theciphersuite_id
is excluded from the “must be prepended with its length” rule when hashing (no reason for it).