|
Steve Fox <drfickle@us.ibm.com> writes:
> Even if your software doesn't contain the crypto code? Isn't it the
> OpenSSL library that does all this?
As I understand it, yes, it's still covered. I think this is what the
"open cryptographic interface" provisions are about - because tn5250
imports functions designed for crypto, export notification is required.
If sslstream.c was distributed as a separate library, then the BXA
wouldn't need to be notified about tn5250, because the Tn5250Stream
interface is not a specifically cryptographic interface. However,
sslstream.c would require notification itself.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.