[
Lists Home |
Date Index |
Thread Index
]
On Friday 03 October 2003 17:58, Miles Sabin wrote:
> Tyler Close wrote,
>
> > I am only saying that it must be feasible to maintain an ASN.1
> > implementation as part of a legacy codebase.
>
> This is only interesting if expressed in relative terms: it must be at
> least as feasible to maintain an ASN.1 implementation as it would be to
> maintain comparable alternatives. I can't think of any particularly
> good reasons for thinking that's not the case.
What about the argument about increasing the complexity of the
lexer, through merging of the parser? You haven't responded to
that.
> > Obviously, OpenSSL and SNMP have had difficulties with that. Are there
> > counter-examples of applications that have not had long-lived bugs
> > in their ASN.1 code?
>
> Would you like some examples of undetected crimes as well? ;-)
A list of legacy apps that use ASN.1, and haven't experienced the
same problems as OpenSSL and SNMP, would do fine. Surely someone
must have safely implemented it.
Tyler
--
The union of REST and capability-based security:
http://www.waterken.com/dev/Web/
|
