|
Wow... I have no idea what they're trying to say on this site. I was under the impression that since we don't do any cryptography in tn5250, and since OpenSSL is a seperately-distributed item, we would not have to deal with all of this. I'm not a lawyer, nor do I have one that I can ask. Does anyone have access to a lawyer that this could be run past? I'd hate to have to hire one for the purposes of free software... On 12 Dec 2001, Steve Fox wrote: > On Wed, 2001-12-12 at 01:36, Carey Evans wrote: > > Now that tn5250 is crypto software, we need to notify the Bureau of > > Export Administration of the location of the source code, for a > > License Exception TSU under 15 CSR §740.13(e). This is described at > > <http://www.bxa.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html>. > > We probably should have done so before checking the OpenSSL support > > into CVS. > > Even if your software doesn't contain the crypto code? Isn't it the > OpenSSL library that does all this? >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.