Salz, Rich wrote:
>
> The folks at the Distributed Systems Technology Center is building
> a PKI from the ground up. They've made similar modifications to
> SNACC. The primary difference is that VanDyke considers their version
> to be frozen ("it does what we need it to do") while DSTC might still
> be doing some work on their version. Oscar is at
> http://oscar.dstc.qut.edu.au/. Given their location I sent them
> a line asking if they'd like to help modify SNACC to work with OpenSSL,
> if only because their follow aussies were involved. :) Haven't heard
> back yet.
Well if the output isn't encumbered by any license then I'd welcome this
and will try provide whatever assistance I can to make it output OpenSSL
ASN1 code.
OpenSSL ASN1 is *very* painful to maintain manually, its given me no end
of headaches :-(
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]
