|
I posted a message to the OpenSSL-Users mailing list asking what other people are doing. It seems odd to me, since we don't actually have any crypto code in the package -- and we don't distribute any crypto code with the package -- that we'd have to file for this. To be safe, I still think we should find a lawyer we can talk to, but maybe the OpenSSL users will have some insight. You'd think that this would be a very common situation! On 12 Dec 2001, 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. > > I could do this myself, although I suspect they'd rather a US citizen > did so. >
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.