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

std/crypto/{25519,pcurves}: make the scalar field order public #11955

Merged
merged 1 commit into from Jun 29, 2022

Conversation

jedisct1
Copy link
Contributor

For 25519, it's very likely that applications would ever need the serialized representation. Expose the value as an integer as in other curves. Rename the internal representation from field_size to field_order for consistency.

Also fix a common typo in scalar.sub().

For 25519, it's very likely that applications would ever need the
serialized representation. Expose the value as an integer as in
other curves. Rename the internal representation from `field_size`
to `field_order` for consistency.

Also fix a common typo in scalar.sub()
@jedisct1 jedisct1 merged commit 41533fa into ziglang:master Jun 29, 2022
@jedisct1 jedisct1 deleted the scalar-field-order branch June 29, 2022 05:45
andrewrk pushed a commit that referenced this pull request Jul 19, 2022
For 25519, it's very likely that applications would ever need the
serialized representation. Expose the value as an integer as in
other curves. Rename the internal representation from `field_size`
to `field_order` for consistency.

Also fix a common typo in `scalar.sub()`.
wooster0 pushed a commit to wooster0/zig that referenced this pull request Jul 24, 2022
…ng#11955)

For 25519, it's very likely that applications would ever need the
serialized representation. Expose the value as an integer as in
other curves. Rename the internal representation from `field_size`
to `field_order` for consistency.

Also fix a common typo in `scalar.sub()`.
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

Successfully merging this pull request may close these issues.

None yet

1 participant