Re: Crypto in Python: (Was: What's so funny? WAS Re: rotor replacement)

2005-01-25 Thread phr
"Philippe C. Martin" <[EMAIL PROTECTED]> writes: > So far getting the agreement for my product has taken two months of work > (http://www.bis.doc.gov/encryption/) I hope to get a positive > response this week (wish me luck!) That sounds like you're doing a closed source product and need an EN

Re: Crypto in Python: (Was: What's so funny? WAS Re: rotor replacement)

2005-01-25 Thread Philippe C. Martin
>In the USA, it's pretty simple, you just send an email to an address >at the BXA telling them what you're exporting. >See http://www.bxa.doc.gov/Encryption for info. I wish it were so :-) So far getting the agreement for my product has taken two months of work (http://www.bis.doc.gov/encryptio

Re: Crypto in Python: (Was: What's so funny? WAS Re: rotor replacement)

2005-01-25 Thread phr
"Philippe C. Martin" <[EMAIL PROTECTED]> writes: > I do not know in which country the python.msi is compiled (Deuchland ?), > but most likely, the county has rules like most other as far as crypto > code in binary format export (especially if distributed as part of a > commercial package): for inst