To rewrite ASN1 code will change almost everything in openssl.
the current nid<-->oid definig, the signing ,verifing of RSA and DSA,
then the cert and request management, PKCS5,7,8,12, then the
SSL handshake, the last but necessary, the demos and apps.
I haven't look into the S/MIME, but I think it will be rewrited too.
Is you the only one being involved in this project? And what is the agenda
of you (or your group)?
> Things are at a very early stage and no code is currently publically
> available, however...
>
> There are quite a few aims for the ASN1 revision.
>
> One goal is to reduce code bloat. As such I want to avoid any option
> that results in lots of code. I'm planning an "intelligent" encoder and
> decoder that gets passed a tiny structure describing the ASN1 structure
> to encode or decode.
>
> It will be possible to hand code the structures with the aid of various
> macros. The result should be much more readible than the current mess
> and vastly easier to write.
>
> It should also be possible to post process the output of an SNACC
> 'template' into these structures too.
>
> Another aim (though not initially) is to support stream based I/O. As a
> result it should be possible (for example) to process enormous PKCS#7
> structures without ever holding all the content in memory.
>
> 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]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
