Michael Sierchio wrote:
>
> Dr S N Henson wrote:
>
> > 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....
>
> Steve -
>
> I would consider it extremely desirable (if not essential)
> that the encoder/decoder use output of an ASN.1 compiler
> rather than solely relying on hand-tooled structures.
>
Well we've struggled along without that so far, but I agree that it
is highly desirable. SNACCs template output seems to be usable in
this regard.
Even without that it should be considerably less painful to hand code
ASN1. The 'template' will only have to be written once and it will then
automatically be usable with the high level new(), free(), encode(),
decode() and print() routines.
Unfortunately most of the existing ASN1 will need to be hand coded into
the new ASN1 structures. One of the trickier problems is to support all
the unusual hacks and quirks in the current code to work around broken
ASN1 encodings.
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]
