David Stes wrote:
> 
> On Fri, Jul 27, 2001 at 07:27:59PM +0100, Dr S N Henson wrote:
> > What field does the Certicom ECC root use, is it available anywhere?
> 
> There's the NIST specifications on ECC (ECDSA) and there's also a
> Certicom group called SECG.  They specify fields.  And curves.  And
> basepoints.  That's a good idea, but I think there's still a lot of
> room ...  Basically there is so much parameters to choose that the
> standards are actually just very few fields/curves.
> 
> It is perfectly easy for OpenSSL to use our own fields and curves.
> 

Well the orignial query was referred to the certicom root. In any case
the dumpasn1 output answered the question it uses the OID 1.3.132.0.1
which is sect163k1 in one of the SECG specs which is a 2^m curve. 

> > It isn't currenly possible to just plug in a new public key crypto
> > algorithm into OpenSSL and it would in any case need ASN1 support with
> > the EC public key format. This would require quite a bit of modification
> > to OpenSSLs core code.
> 
> This is what I was trying to do.
> 
> I found the ASN1 writing was getting close (reading not yet so close,
> but I'm going to get there .....
> 
> but I loose time because I have to keep in sync with you, I first had
> a patch for OpenSSL 0.9.6 and later for 0.9.6a and it is some work to
> keep in sync.
> 

Well the ASN1, as you may have noticed, has been completely rewritten
for 0.9.7 and it should make life somewhat easier. There are also some
prime field ECC operations in crypto/ec, though as I said no 2^m stuff
which would be needed to verify the certicom root.

Steve.
-- 
Dr Stephen N. Henson.   http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED] 
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the   OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to