Export Restrictions on .NET ??

  • Thread starter Thread starter Emby
  • Start date Start date
E

Emby

There used to be restrictions on the export of "enhanced encryption" (which
usually meant encryption with a strength greater than 40-bit) to certain
"restricted countries" (Cuba, Iran, Iraq, Libya, North Korea, Sudan, Syria
and Vietnam - the list varies over time)

But v2.0 of the ,NET framework includes strong encryption (128-bit). Does
that mean that ALL .NET applications are restricted from being exported?

Thanks,

Emby
 
Since the encryption is in the run time library and not the applications,
generally it means no, you are not restricted.
Now if you include the .Net runtime as part of your instalation, then yes,
it might be restricted.

The exception would be if you were to use weak encryption in a way that
strengthens it - then it might be restricted.

In all cases, if you export (anything) to any of the currently restricted
countries, you would be wise to have legal council involved anyhow.
 
I guess it means that ONLY application using this encryption algorithm
directly are restricted.
For exemple I don't use them in my application, so it's all good!
 
Thanks Mike,

That's kind of what I was thinking ...from
http://msdn2.microsoft.com/en-us/library/ms925919.aspx

Getting a CSP (Cryptography Service Provider) Signed
"In accordance with the U.S. Department of Commerce's export restrictions
concerning cryptography, Microsoft must digitally sign every CSP so that it
will run on Microsoft operating systems. The primary purpose of the digital
signature is the protection of the system and its users. The operating
system validates this signature periodically to ensure that the CSP has not
been tampered with. A secondary effect of the digital signature is that it
separates applicable export controls on the CSP from the host operating
system and applications, thus allowing broader distribution of
encryption-enabled products than would be possible under other
circumstances"

Which seems to indicate that applications that use the Windows CrytopAPI
(and I think .NET apps call into the .NET Framework, which in turn calls the
CryptoAPI) are not themselves restricted.

Cheers
 
Back
Top