-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unable to verify signatures created with a seed #22
Comments
Thanks for your report! I'm looking into this. |
The obvious problem is that the seed has to be |
Looks like it's a length problem:
not sure why it doesn't just read 32 bytes past the pointer, though... (Although it still wouldn't be repeatable) |
@lvh should that error out/throw an exception is < |
Calling
caesium.crypto.sign/keypair!
with abyte[]
seed seems to trigger verification failures withverify(sign ...)...)
.I modified one of the test cases in
sign-test.clj
as seen in https://gist.github.com/talios/d0ea678b0ce5b044ec48c6074855cf6a which triggers the problem.Is this not the correct way to generate a keypair with a common seed, which will survive VM restarts?
The text was updated successfully, but these errors were encountered: