[C#] Recommended Activation Technology

[M_Lyons10]

Hi everyone. I was wondering if anyone could suggest a product (Hopefully reasonably priced) that I would be able to use to provide activations of a .Net project I am working on. I would prefer something that I would be able to use on more than one project, but as sales are likely to be relatively small, cost is a concern. So I was curious if anyone had any good suggestions for me.

Thanks Again,

[garethevans1986]

I had this problem with a product I'm developing...then decided to move the product to a web based solution...problem solved.

PM sent.

GE

[M_Lyons10]

Thank you very much for your response. Unfortunately due to the information I'm storing in the application I don't think I would be able to move this to a web based solution... I've been looking at a few options, but I honestly don't know what would be a good solution for this. I'm really hoping that we get a few recommendations of solutions others have used and such. :)

I did find this and it sounds decent, but I'm not sure what others would think about this solution:

http://www.eziriz.com/intellilock.htm

[firey]

I coded my own, that generates a key server side, and is returned to the client, if the client and server both match it's good to go. I know there are potential risks (code being exposed), but depending how you do it, can be pretty secure. Especially if the server sends a message to flip a random bit based on some random code.

[M_Lyons10]

Thanks for the response. I appreciate the suggestion. I'm not sure that I would want to make my own though, considering the potential if I made a mistake. I want to make sure that it isn't too restrictive, but on the same token isn't going to have a flaw or something that would allow anyone to use my application. :(

[firey]

Thanks for the response. I appreciate the suggestion. I'm not sure that I would want to make my own though, considering the potential if I made a mistake. I want to make sure that it isn't too restrictive, but on the same token isn't going to have a flaw or something that would allow anyone to use my application. :(

The way mine works, is the client generates a key (based on a formula), the client sends it to the server where the server stores it. If it is a valid key the server sends back another code that contains an encryption key and an encrypted key. The client then runs a formula, uses the encryption key and compares it's internal result with the one the server sent. If it works I save some files that the user doesn't know about. Granted there are potential security flaws, I never let the customer see their product key, when they do it is fully encrypted, and I have redundant copies of their key all over the place. I use 2 token files, and embed their key into the licensing program. All the data is encrypted as it travels. Basically I hide as much as possible from the client. Even the offline activation uses their unique key with a formula based on bits within the program that I turn on and off and it is then read to our support staff which can decode the key, and generate an auth-code which in turn has a key built into it, that when compared inside the client if it matches it is good.

It's pretty simple, the biggest thing is making it very dynamic in that it's not just a simple formula, make it change based on different factors, and spread the code out as much as possible instead of keeping it to one area in code. Also hide whatever security measures you use from the client.