Preventing end users from using copies of your front end - the solution

I have not been cracked since '87, of course I have only had about 300 clients, it is not industrial or massive, I did not have the necessary capital to do it well, and sell it as a standard package, dealing with clients and their adaptations was very personal, but After several sales, the adaptations worked for everyone and I had a fairly commercial product.
That is your experience from your particular point of view. However, it's unlikely that someone who found a way to avoid paying for your product will confess to bypassing your protection. I, on the other hand, once had a call from a customer complaining about my software and I found out he was using an illegal copy of it. Someone was distributing it without my permission. One part of me was flattered, the other one was furious, with myself, for thinking an accde file would be secure. That software, which calculates 3D spots and plots them into a niche 3D application for construction boundary surveyors is now used by who knows how many people now, but I'm turning it into a .NET application to avoid this. I hope others don't go through that.

The point is, don't trust in Access' securitus.
 
Something similar happened to me but it was my partner cheating, and then we separated
 
I get that personal applications, especially games, are subject to pirating but business applications, especially vertical market applications, not so much. Why would a company give your software to a competitor? They would be more inclined to violate their seat license count. Apparently, in @Edgar_'s case they were selling it. Assuming you can link a specific copy of the software to a specific client, that should be a slam-dunk (basketball reference) of a lawsuit. I limit some of that problem by including an expiration date in my license key.
I understand what you are telling me and it is true, you are very right, the problem is that there are other people who make systems and that the demos and some software already working give them ideas to make their own, this web control also allows you to cut the system If it is for rent or multiple payments (lising), if the client does not pay more.

But the idea is to answer this friend with software protection alternatives
 
Just a thought.

Is there ever a situation where the software can think a given user is logged in when he isn't, perhaps due to a system crash, or similar.
Is there a way of clearing a login record so the registered user can log in again?
Can that be abused in any way to allow unregistered access?
 

Users who are viewing this thread

Back
Top Bottom