Hi Doug,
After extracting the private key from the testkey.pem file and putting it into
the vendor's tool file format, the vendor tool generated digest ends up
looking
like:
E39C9EEB4A60BFAF93235B376E9E54883C127BC40300
F4760E34AC2ECB484B2DFF06E87113C9F1F9F99F0200
Ah! Now I see
Thanks much for the explanations on how this data is laid out.
My first attempts at using the key I generated on my hardware platform were
unsuccessful.
Stepping back, I thought I would use openssl to create a sect163k1 encrypted
SHA1 digest of my test file and then verify it. I have been able
From: owner-openssl-us...@openssl.org On Behalf Of Jeffrey Walton
Sent: Wednesday, 21 October, 2009 18:09
Just a few small tweaks:
First, generate the domain parameters:
openssl ecparam -genkey -name secp160k1 -out c:\key.pem
Next, strip the PBE:
openssl ec -in c:\key.pem -out
Doug: It is my understanding that the first byte of the public key is a flag
to indicate if the public key is compressed, uncompressed or hybrid:
-conv_form arg specifies the point conversion form
possible values: compressed
- Jeffrey Walton noloa...@gmail.com wrote:
Hi Doug,
I am trying to figure out where the padding bits
are applied?
...
The two private keys are described in a different
number of bytes. Since the 2nd generated private
key is shown in 20 bytes i.e. 160 bits, is it assumed
that
Hi Doug,
You'll have to forgive my ignorance. I'm not sure why I'm having
difficulties answering you. I'll try to walk you through what I
observe.
I'm a Windows guy, so don't hold it against me that I use 'type'
instead of 'cat'. I'm also going to use F(p) rather than F(2^m) since
I believe its
I have been trying to generate keys for a ECDSA system that uses a sect163k1 key
pair.
In generating some of the key sets, I notice that the printed length of the keys
differ when using the -text command option. Since openssl is displaying a 163
bits in a byte-wise display, I am trying to figure
Hi Doug,
I am trying to figure out where the padding bits
are applied?
...
The two private keys are described in a different
number of bytes. Since the 2nd generated private
key is shown in 20 bytes i.e. 160 bits, is it assumed
that the MS 3 bits are 0?
The public key, also known as the
