isislovecruft commented on May 5, 2017 First things first: @petertodd, you've publicly, repetitively defended a man who raped me
PublicKey::from_bytes() docs could be a bit more helpful #4
Comments
First things first: @petertodd, you've publicly, repetitively defended a man who raped me and several other people, and disparaged the victims who were brave enough to come forward with their stories. Do not speak to me. Do not use work as an excuse to speak to me. Do not use cryptography as an excuse to speak to me.
Now, lest someone say I didn't address your "issue". Both methods are labelled with a giant Warning header, so I'm not sure I see the problem. If you do:
And then you later do:
Then everything will work out fine. If you do anything else, e.g. use a hypothetical broken library¹ to generate the keys, or somehow handcraft your own artisanal broken key, then
ed25519-dalek will be unable to verify signatures, because curve25519-dalek will fail to decompress the point.
¹ FWIW, I've no reason to believe there is any incompatibility between
ed25519-dalek and other current implementations (and the ed25519-dalek tests call SecretKey::from_bytes() and PublicKey::from_bytes() on keys generated with another implementation). |
petertodd commentedon May 5, 2017