Secure DLL

[Jurgen]

Hello,

I'm looking for a way to protect some C# libraries (DLL's) with serial
keys to prevent unauthorized use and/or copying and/or installing. I've
seen allready a number of products, but they only seem to work with
applications (.exe). Can anyone recommend me such a product?

kind regards,

 

[Bob Powell [MVP]]

Infralution provides a very good method.

http://www.infralution.com


--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

 

[Bob Powell [MVP]]

Remember that to protect any .NET DLL, especially one with any sort of key
or serial number code included obfuscation is of paramount importance.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

 

[Guest]

I assume that you have heard of strong-named assemblies in .Net. This would
make your DLL a secure DLL but to make it accessible only in an authorized
way, you may need to secure it further. For instance, you can configure an
assembly with specific access permissions based on some parameters like
strong name key, publisher signature, URL, etc. So, if you secure your dll
with a publisher signature then only applications containing the signature
will be able to reference it; or, if you use public key as the condition for
acces, then only those apps with the same public key would be able to
reference your dll. Even if someone does copy your dll to some other
location, it would not help unless that someone also has the same public key
or signature.

Regards,

Jv

 

[Jurgen]

Remember that to protect any .NET DLL, especially one with any sort
of key or serial number code included obfuscation is of paramount
importance.

ok, thanks, I'll take a look at it.