Richard Levitte - VMS Whacker wrote:
>
> Oh well, I'll keep silent about this 'til somone else in the team says
> something...
>
Well my 2p is that well have to break lots of things until the API is
more stable and some of the broken or just plain silly things will be
junked or replaced in an incompatible way with each release.
In other words at present applications should be relinked with each new
release or bad things almost certainly will happen. I can think of
several things that would fail subtly or not so subtly even without the
stack change. The stack change at least has the virtue of being obvious
:-)
BTW any changes in the current code are as *nothing* when compared to
what the ASN1 code revision will have to do.
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]
