Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 to new
Scalar
API #293Update to new
Scalar
API #293Changes from all commits
69706a4
7ea4300
74cb956
bf5d2cf
67524b2
92afd3e
cd1334d
06f5517
652d151
da33aa4
bcee905
9a2b296
1cf99d7
36808fd
a467ca3
997e4ed
c67428e
df466f8
651c04e
955739f
c1c9b44
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
I guess I overlooked this before.
@rozbb there are use cases like Ed25519-BIP32 where the private scalar is computed rather than clamped from bytes.
Adding this field means you can no longer construct an
ExpandedSecretKey
directly from a derivedScalar
and prefix using the struct literal syntaxExpandedSecretKey { scalar, hash_prefix }
and have to go through one of the constructor methods.I guess the best you could do now if you have a
scalar
and ahash_prefix
is to serialize the scalar withScalar::to_bytes
and concatenate it with thehash_prefix
and useExpandedSecretKey::from_bytes
?Also all that aside, I find a mixture of public and private fields weird. If you really want to go down this path it would probably be good to make
scalar
andhash_prefix
into methods, removing the fields frompub
visibility.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.
Opened a PR to make the other fields private: dalek-cryptography/curve25519-dalek#544