Matt,
You are correct, using the standard installed libraries for Ubuntu 12.10
(OpenSSL 1.0.1 14 Mar 2012), my test app successfully creates EC keys and
successfully sign and verify some data for all types of curves of all sizes.
The private key however seems to be bigger (more chars in PEM
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
On 20 March 2013 19:44, Steve Marquess marqu...@opensslfoundation.com wrote:
There are tools of a sort to convert between docbook, pod, and markdown.
I've played with a couple of them, but I think annoying little details
will keep such tools from representing any net labor savings over manual
On Thu, Mar 21, 2013, Leon Brits wrote:
Stephen,
Just to clarify that a bit. EC keys are most comonly represented by named
curves instead of explicit parameters. Unfortunately the default is to use
explicit parameters and there's nothing (yet!) at an EVP_PKEY level to
change that.
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
Hi Leon
On 21 March 2013 17:27, 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
Per F5 Product Development, the log message quoted in the previous note is not
related to ID 376483. It is a cosmetic issue which may be safely ignored.
Amy Wilhelm
Enterprise Network Engineer
F5 Networks
__
OpenSSL Project
Hello!
I'm currently using the cryptodev framework-engine with openssl-1.0.1e.
By run the command
# openssl engine -t
(cryptodev) cryptodev engine
[ available ]
(dynamic) Dynamic engine loading support
[ unavailable ]
we can see that the cryptodev is the active-chosen engine.
So it