| | |
DLL protection
Please support our C# advertiser: Intel Parallel Studio Home
![]() |
•
•
Join Date: Mar 2008
Posts: 18
Reputation:
Solved Threads: 0
Hi I have a quick question, I tried asking on the MSDN forums and they were no help.
I am wondering how I may protect my DLL files from being used by other people. By "used" I mean, referenced/imported or whatever into projects and the functions and variables inside used.
I only wish it to be used by my applications... is there a way to protect it?
Thankyou for any help you may give me.
I am wondering how I may protect my DLL files from being used by other people. By "used" I mean, referenced/imported or whatever into projects and the functions and variables inside used.
I only wish it to be used by my applications... is there a way to protect it?
Thankyou for any help you may give me.
•
•
Join Date: Mar 2008
Posts: 18
Reputation:
Solved Threads: 0
Just seems so absurd this kind of thing isn't already built-in.. I mean.. dlls are supposed to be useful to the programmer so he can share things between his applications but not everyone else... :/ it annoys me the .net language is so open too... you can decompile the apps so easily it's not worth the effort inventing new functions just to have them stolen.
•
•
Join Date: Mar 2008
Posts: 1
Reputation:
Solved Threads: 0
There's actually an easy method in the CLR to limit the use of your assemblies to only your projects. Take a look at the PublisherIdentityAttribute in the docs. This will limit the use of your assemblies to assemblies signed by your private key - effectively limiting the use to those you authorize.
Of course with all the other security weaknesses in .NET this can be circumvented without proper proptection of your assembly. You'll want to take a look at an obfuscation/encryption tool to make sure the strong names can't be modified. CodeVeil - by XHEO where I work - will do just that.
Of course with all the other security weaknesses in .NET this can be circumvented without proper proptection of your assembly. You'll want to take a look at an obfuscation/encryption tool to make sure the strong names can't be modified. CodeVeil - by XHEO where I work - will do just that.
![]() |
Similar Threads
- Suggested Protection (Windows 95 / 98 / Me)
- "WINDOWS\ SYSTEM\ BRIDGE.DLL" (Viruses, Spyware and other Nasties)
- C:\system32\bridge.dll module cannot be located (Viruses, Spyware and other Nasties)
- about:blank hijack (can't find any .dll-file) (Viruses, Spyware and other Nasties)
- bridge.dll problem (Viruses, Spyware and other Nasties)
- Bridge.dll...Make it go away, Plz (Viruses, Spyware and other Nasties)
- Another problem with BRIDGE.DLL (Viruses, Spyware and other Nasties)
Other Threads in the C# Forum
- Previous Thread: how to add watermark in image
- Next Thread: SQL TimeStamp in DataViewGrid
| Thread Tools | Search this Thread |
.net access ado.net algorithm array barchart bitmap box broadcast button buttons c# check checkbox client color combobox control conversion csharp custom database datagrid datagridview dataset datetime degrees development draganddrop drawing editing enabled encryption enum event excel file files form format forms function gdi+ httpwebrequest image index input install java label list listbox listener load mandelbrot math mouseclick mysql operator path photoshop picturebox pixelinversion post print programming radians regex remote remoting resolved. richtextbox save saving serialization server sleep socket sql statistics stream string table tcp text textbox thread time timer update user usercontrol validation view visualstudio webbrowser windows winforms wpf xml





