Closed andres-erbsen closed 12 years ago
This happens regardless of whether I'm using Ed25519 or not. I'm still investigating.
Something interesting is that while in 2b27a0f7b15ac6a33adbf8981a657f80ca76c815 I added a test that caused failure on my machine, the travis-ci.org build slaves correctly function and run all the tests(see build #12.) The main difference I can see is that the build slaves are x86 and we're using 64 bit machines.
Nothing conclusive yet, but noting it.
Trying to verify a a invalid signed message that is shorter than it should be results in segfault.
Full log: