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
In Test.Shelley.Spec.Ledger.Utils, the mkGenKey, mkKeyPair, ..., functions, which use mkSeedFromWords are broken for some instantiations of crypto. I believe they work fine for mock crypto, which is what they're mostly used for, but not for all crypto, e.g., real crypto.
The problem is that some crypto algorithms need bigger seeds than mkSeedFromWords gives. mkSeedFromWords uses the MD5 algorithm to create hashes, which means these hashes are always 16 bytes. But Ed25519DSIGN needs a 32-byte seed.
The solution would be to use seedSizeDSIGN, seedSizeKES, seedSizeVRF, ..., to generate a seed of the right size, e.g., by repeating/concatenating/rehashing until the right size has been reached.
The text was updated successfully, but these errors were encountered:
In
Test.Shelley.Spec.Ledger.Utils
, themkGenKey
,mkKeyPair
, ..., functions, which usemkSeedFromWords
are broken for some instantiations of crypto. I believe they work fine for mock crypto, which is what they're mostly used for, but not for all crypto, e.g., real crypto.For example:
The problem is that some crypto algorithms need bigger seeds than
mkSeedFromWords
gives.mkSeedFromWords
uses the MD5 algorithm to create hashes, which means these hashes are always 16 bytes. ButEd25519DSIGN
needs a 32-byte seed.The solution would be to use
seedSizeDSIGN
,seedSizeKES
,seedSizeVRF
, ..., to generate a seed of the right size, e.g., by repeating/concatenating/rehashing until the right size has been reached.The text was updated successfully, but these errors were encountered: