>
> Examples would be certificate extension code, message digest algorithms
> or stuff related to authentication only (e.g. DSS).
>
> Or do you think even contributions of this sort could cause problems?
I beleive that this would be a problem because that would be a
US person providing technical assistance in the development of an
encryption item.
One potential solution to this problem, however, could be the
creation of multiple different products. I.e. an ASN1 toolkit,
etc. However, I don't think that's worth the hassle.
BTW -- its my understanding that even though
authentication-only cryptography is exportable, it still requires a
license. Therefore a DSS toolkit, for example, may still have problems
with getting US contributions.
--
[EMAIL PROTECTED] 510 291 2283
The BPM Group http://www.bpm.ai/~sameer/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
