Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have been asked to look into providing a client with a solution for Licensing and code obfuscation. I am no security expert and so I am not even sure exactly what is involved or where to start for providing these features for the client. Any suggestions on reading material or even full solutions would be appreciated (open source over comercial solutions).
Please refer: CryptoLicensing for .NET
Thanks
Depending on the expected amount of users and deployment strategy SafeNet may be an option for you.
At my former company we used the HASP HL product for protection of .NET applications for several years and it works nice and reliable. This is a hardlock based solution, but it is also compatible with Aladdin’s software based SRM solution.
The companies portfolio is very flexible, you can deploy the same application software protected, hardware protected, as trial versions, …
You can create different packages features and/ or protect the application file with an envelope that requires the hardlock (HASP HL) or an windows-like activation (SRM).
Runtimes are available for the most common operating systems.
You can protect .NET or natively complied applications, Java applications, or simply data files and documents.
According to their own information, Aladdin is one of the world’s biggest players in software protection. Since they fused with SafeNet two years ago, their portfolio should have grown even to a broader product offering than I am aware of, since I do not use this stuff at my current employer.
As a side note, Aladdin makes sure that the products remain backwards compatible as long as possible. For the mentioned project a t the former employer, we had a more than 6 year old .NET 1.1 legacy application in the field and it still ran with the latest drivers.