I'm also a bit suspicious about the OIDs of secp192r1 and secp256r1.
In obj_dat.h they both end up having OID 0. Their corresponding OBJ_
macros in obj_mac.h get mapped to OBJ_X9_62_prime{192,256}v1 (of which I
suppose they are aliases), though, so it may be OK.
I'm not into all the
Hello,
I was in for a surprise when I added some custom objects into objects.txt.
Since I wanted to use our private enterprises OIDs, I used the form:
enterprises 1527 1 : myobj : My Object
(same form as the dcObject already in there)
However, enterprises is undefined, so my
On Thu, Apr 04, 2002 at 12:23:26PM +0200, Svenning Sorensen wrote:
Since I wanted to use our private enterprises OIDs, I used the form:
enterprises 1527 1: myobj : My Object
(same form as the dcObject already in there)
However, enterprises is undefined, so my object ended up
From: Svenning Sorensen [EMAIL PROTECTED]
sss I was in for a surprise when I added some custom objects into objects.txt.
sss
sss Since I wanted to use our private enterprises OIDs, I used the form:
sss
sss enterprises 1527 1 : myobj : My Object
sss
sss (same form as the dcObject
At 20:40 04-04-2002, Richard Levitte - VMS Whacker wrote:
To be perfectly honest, I think you're dong this the wrong way. I
assume you're using the openssl command to do stuff, and in the case,
the right thing is to have the desired extra OIDs in openssl.cnf.
[snip]
If you're building an
