You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2021. It is now read-only.
The documentation states entropy must be "at least" 16 bytes long, suggesting longer arrays will be accepted and utilised. However, the code truncates supplied arrays of length>16 to the first 16 bytes, without returning an error.
Which is the correct behaviour?
As it stands, the module may be supplied with a large array of entropy in good faith, only to have this reduced to the first 16 bytes without notification. A user of the module may be lead to believe seeds are being generated with a greater amount of entropy than is in fact taking place.
The text was updated successfully, but these errors were encountered:
Create a shitload of entropy and hash it to 128 bits??
See the ripple-lib issue/pr where someone is requesting to be able to use
keypairs (32 byte secrets) directly to sign txns. With that enabled you can
create that 256 bit priv key anyway you want :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The documentation states entropy must be "at least" 16 bytes long, suggesting longer arrays will be accepted and utilised. However, the code truncates supplied arrays of length>16 to the first 16 bytes, without returning an error.
Which is the correct behaviour?
As it stands, the module may be supplied with a large array of entropy in good faith, only to have this reduced to the first 16 bytes without notification. A user of the module may be lead to believe seeds are being generated with a greater amount of entropy than is in fact taking place.
The text was updated successfully, but these errors were encountered: