There's an issue relating to the new ASN1 code relating to how it
declares the ASN1 functionality. This could cause some pain later on so
best to mention it now...

If you've been following how it works (and if you haven't then you can
try  BRANCH_ASN1: but I warn you its experimental and not too pretty
just yet) then you'll know there are some high level functions that are
called with a constant C structure. The normal one is called ASN1_ITEM
and when the macros are expanded you'll have something like this:

const ASN1_ITEM something_it = {...};

(there is a naming discipline in the macros that forces these to end
with _it). The normal functionality is obtained by some typesafe wrapper
functions so something_new() calls ASN1_new(&something_it); . These
don't actually have to be wrapper funtctions: they could be typesafe
macros that mean that there are no i2d/d2i/free/new functions at all.
Even if you don't go down the pure macro route applications that define
their own ASN1 code will almost certainly need access to some of the
libraries internal something_it structures.

Anyway there's no problem doing &something_it in the core code. There's
no problem with static libraries either. The bit that could cause
problems is how or even if you can do this with shared libraries.

I tested Linux and it seems to work transparently and painlessly.

Can anyone forsee problems? I'm expecting Windoze to be fun as usual...

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
Team Mailing List                             [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Team Mailing List                             [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to