On 21 March 2013 09:06, Leon Brits <le...@parsec.co.za> wrote: > > First off the private key created with the "sect233r1" curve are: > -----BEGIN PRIVATE KEY----- > MHYCAQAwCQYHKoZIzj0CAQRmMGQCAQEEHVnVyx1BHVTaKFSi758nc0v1SnWNQ1aR > BYRjL4ZboUADPgAEAVZmnrloR8NnuKI7pzD8n8UYXHannulPUv2JVqeiAXI1bnBR > K10brlEGKzKztusdvxC6UVz1Ew9eVvcL > -----END PRIVATE KEY----- > > It does contain less information - I am not an expert but this seems wrong?
Yes, they are corrupt. You can take a look at them with: openssl asn1parse -in in.pem -i Comparing them with a "good" key, you can see that they are missing a lot of information. > > So, to conclude: It seems that this is a FIPS related problem. The keys > simply seems incorrect and will therefore cause all the errors I now see. > But, I do not get why a will get different errors when reading the exact same > PEM formatted key. Or, why it all works for NIST prime curves? > I'm afraid I'll have to let others on this list assist with this. I am not familiar with the FIPS builds. :-( Matt ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
