FYI,
My Build system and target system have similar OS.
Build System: x86_64 x86_64 x86_64 GNU/Linux
Target System: x86_64 GNU/Linux
--
View this message in context:
http://openssl.6102.n7.nabble.com/FIPS-module-Algorithm-tests-failure-tp44420p9.html
Sent from the OpenSSL - Dev mailing
Hi Matt,
I use:
$ openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
I was able to successfully parse your attached private key.
I've attached my smallest prime, binary and kolbitz curve key pairs. As I said
the prime curve parses correct with the openssl command line tool but not the
binary
Hi Matt,
Can you send me an offending PEM file?
I've replied with this information attached to your second message
They are different formats. If it has BEGIN PRIVATE KEY it is in PKCS
8 format. See:
https://www.openssl.org/docs/apps/pkcs8.html
If it says BEGIN EC PRIVATE KEY then its as
List,
I've continued so long to use the NIST prime curves to implement sign/verify
using EVP. I am basically using the same code as for RSA and DSA. This
mechanism is so transparent (nice!) that I just want to verify that it is using
ECDSA at the backend? Do you have any reference to this
On 20 March 2013 10:36, Leon Brits le...@parsec.co.za wrote:
List,
I've continued so long to use the NIST prime curves to implement sign/verify
using EVP. I am basically using the same code as for RSA and DSA. This
mechanism is so transparent (nice!) that I just want to verify that it is
On 03/19/2013 07:49 PM, Pierre DELAAGE wrote:
Hi Steve,
My own experience in my company is that OpenOffice is perfectly suited
for track changes in a collaborative env.
Ok, allright, it cannot offer a line by line diff as in cvs systems, and
return to specific version and so on, but the track
On Tue, Mar 19, 2013, Cipher wrote:
I am cross compiling FIPS object module as per FIPS user guide 2.0. After
creating fipscanister.o, i tried *make build_tests* to generate
*fips_test_suite file*, which i could run successfully(both in build system
and target system).
But When i try
On Wed, Mar 20, 2013, Leon Brits wrote:
List,
I've continued so long to use the NIST prime curves to implement sign/verify
using EVP. I am basically using the same code as for RSA and DSA. This
mechanism is so transparent (nice!) that I just want to verify that it is
using ECDSA at the
On Fri, Mar 15, 2013, Dr. Stephen Henson wrote:
The only real quirk is that when you generate a key the named curve ASN1
option isn't set by default for keys and can't be set by a ctrl. You can
extract the key and set that manually though.
Just to clarify that a bit. EC keys are most
On 19 March 2013 18:53, Steve Marquess marqu...@opensslfoundation.com wrote:
On 03/19/2013 10:47 AM, Pierre DELAAGE wrote:
Dear Steve, I was wondering whether the wiki could be fed at the
beginning by all the Documents available at
http://www.openssl.org/docs/;.
Very often people are able to
On 19 March 2013 23:27, Steve Marquess marqu...@opensslfoundation.com wrote:
On 03/19/2013 04:59 PM, Matt Caswell wrote:
On 19 March 2013 19:38, Steve Marquess marqu...@opensslfoundation.com
wrote:
I took a quick look to see what utilities might be available to convert
between pod and
On 03/19/2013 03:15 PM, Ben Laurie wrote:
...
Very often people are able to comment, eg, a command page with some
samples or error comments, instead of rewriting from scratch a man
page.
And this could be a way to only have one unique set of docs to
maintain, and to refer to, instead of
On 20 March 2013 07:14, Leon Brits le...@parsec.co.za wrote:
Hi Matt,
I use:
$ openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
I was able to successfully parse your attached private key.
I've attached my smallest prime, binary and kolbitz curve key pairs. As I
said the prime curve parses
On 20 March 2013 07:27, Leon Brits le...@parsec.co.za wrote:
Thanks for that explanation - so, just to understand the history, why is
there no secp256_r1 as well as the ANSI standard curve. In other words, why
does the ANSI curve replace it instead of being an additional curve?
I have no
On 3/20/2013 4:24 PM, Matt Caswell wrote:
On 20 March 2013 07:27, Leon Brits le...@parsec.co.za wrote:
Thanks for that explanation - so, just to understand the history, why is there
no secp256_r1 as well as the ANSI standard curve. In other words, why does the
ANSI curve replace it instead
On 20 March 2013 21:11, Matt Caswell fr...@baggins.org wrote:
On 20 March 2013 07:14, Leon Brits le...@parsec.co.za wrote:
Hi Matt,
I use:
$ openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
I was able to successfully parse your attached private key.
I've attached my smallest prime, binary
16 matches
Mail list logo
