You are correct in that statement. How ever I'm still trying to clerify a few little potential snaggs.
>From what I've seen a "permit" may be required, for export / downloads to non-US locations. "Hosting" servers may need to have the ability to deny downloads to locations that shouldn't have it. (don't ask me, I'm just reading this stuff) While it has relaxed, it still appears to be full of red tape. If anyone else is checking on this, let me know if you find any documention that makes sense :-/ ----- Original Message ----- From: "Marco A. Zamora Cunningham" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 25, 2002 11:48 AM Subject: Crypto Export restrictions (was: Apache_1.3.26-Mod_SSL_2.8.10-OpenSSL_0.9.6g-Win32.zip) > Cliff Wooley: > > But there's a reason we can't distribute crypto > > binaries from apache.org -- if we could, we > > would. Guess we wait for Ralf to check up on > > the contrib area. > > Correct me if I'm wrong, but I thought that ITAR restrictions eased up about > a year ago, so OpenSSL strong crypto can now be exported with no problems > *except* to specially targeted countries like Iraq. Case in point: MSIE 6 > includes strong SSL (buggy but strong) and you can download it off > microsoft.com with no restrictions. I vaguely remember downloading a strong > crypto Mozilla or Opera or something like that some months ago by just > filling in a form saying that I'm not a terrorist and I don't live in Cuba, > Iraq or such. > > żIs there anybody here on the cypherpunk lists who can clarify? > > MZ > ______________________________________________________________________ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
