Protect ASP.NET application [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.

---

开发者_如何学运维

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 7 years ago.

Improve this question

Imagine, I create an application ASP.NET MVC for a customer. This application is running an a local server of my customer (I call it customer1). Is there a way to make this application impossible to run foranother customer if customer1 give application to customer2 ?

Thanks,

---

Why are you bothering and wasting your time with things like this? Make sure you license your code, probably obfuscate it, and sell it to a customer. If he violates the license agreement and gives it to someone else that's his problem. Sue their asses and that's it, end of the story. But remember that no matter what you do they will find a way :-)

So focus on delivering a good product and customers will come by themselves to you asking you to buy it.

---

You could hardcode in a check for the domain it's running on perhaps. Simple but crude.

---

I think adding some checking to application start is not a bad idea. checking Computer name and Mac address doesn't seem bad.

---

1- check in your code for a value placed in a file has an encrypted data. this file generated on windows root or some root the customer1 not know it. this file will generate in activating through online connection or by yourself.

in runtime read file and decrypt, you may read values for expired date, some configuration you want.

you may check for as friends said for computer name, ip address anything difference customer1 from customer2

2- also you need to protect dll files from decompilation methods

My Regards

---

It's a Web Application -- the easiest way is to host the application for your customer, that way they won't be able to get the source for it.

---

Most applications use business rules, naming conventions, assets, etc. that are unique to their business. Hard code those values into your app so that a shared app just doesn't apply to another customer.

Beyond that, you can look into a real copy-protection package like DeployLX, Infralution or Desaware.

---

Take a look at Rhino Licensing.

James Gregory wrote a nice post on how to get started with it.

Also the link to a post by Balsamiq in James' article is well worth a read.