I'm trying to get a handle on how python intersects with
crypto-related export control laws in the US and elsewhere. My current
understanding, per the PSF's wiki, is that any crypto related and
potentially export-sensitive code is in the ssl wrapper, and that, in
fact, this only links
Austin Bingham wrote:
I'm trying to get a handle on how python intersects with
crypto-related export control laws in the US and elsewhere. My current
understanding, per the PSF's wiki, is that any crypto related and
potentially export-sensitive code is in the ssl wrapper, and that, in
fact
M.-A. Lemburg m...@egenix.com (M-L) wrote:
M-L Depending on how close a country follows the Wassenaar
M-L Arrangement (http://www.wassenaar.org/) OpenSSL, Python
M-L and all other open-source software falls under the
M-L GENERAL SOFTWARE NOTE part 2.:
M-L
M-L The Lists do not control software
Piet van Oostrum wrote:
M.-A. Lemburg m...@egenix.com (M-L) wrote:
[ ... ]
M-L
M-L The Lists do not control software which is either:
M-L 1. ...
M-L 2. In the public domain.
M-L
[ ... ]
But Python is not in the public domain. Open source != public domain.
Public domain means there is no
Ben Finney ben+pyt...@benfinney.id.au (BF) wrote:
BF Piet van Oostrum p...@cs.uu.nl writes:
But Python is not in the public domain. Open source != public domain.
BF One always needs to be aware of what bizarro-world definitions these
BF legalese documents are using for terms we might normally
Piet van Oostrum p...@cs.uu.nl writes:
But Python is not in the public domain. Open source != public domain.
One always needs to be aware of what bizarro-world definitions these
legalese documents are using for terms we might normally understand.
However, in this case it seems fairly sane and :
Piet van Oostrum wrote:
M.-A. Lemburg m...@egenix.com (M-L) wrote:
M-L Depending on how close a country follows the Wassenaar
M-L Arrangement (http://www.wassenaar.org/) OpenSSL, Python
M-L and all other open-source software falls under the
M-L GENERAL SOFTWARE NOTE part 2.:
M-L
M-L
