USA export restrictions for .NET Framework due to security feature
From: dotNETDavid (dotNETDavid_at_discussions.microsoft.com)
Date: 01/26/05
- Next message: dotNETDavid: "Are there export restrictions due to .NET security code in Framewo"
- Previous message: kishore: "Padding issue with C++ Crypto RC2 encryption"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 26 Jan 2005 11:03:06 -0800
Since the .NET Framework includes encryption/decrytion code, are we
restricted regarding exporting our applications written in .NET?
Do export restrictions, if any, apply whether or not we include code that
calls encryption features in the Framework?
If we include code that uses 192-bit Triple-DES decryption (no encryption)
for a piece of data included with our product, are we subject to export
restrictions?
Thanks for the help!
- Next message: dotNETDavid: "Are there export restrictions due to .NET security code in Framewo"
- Previous message: kishore: "Padding issue with C++ Crypto RC2 encryption"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|