Tips to protect your software from piracy?

[ozzyman]

Obviously, you can't stop every mad scientist from unlocking or copying your software. But the idea is to prevent the average user from getting on to it. So what are the best methods?

I'm not too keen on key activation ALONE as debugger tools allow users to easily switch JUMP statements to the valid activation code/password.

In fact, I don't think any thing alone is secure enough; you need as much protections as possible. So it would be nice if everyone shared their ideas.

I think the best thing is requiring a user to register and login, but that limits your software to users with internet only.

What steps would you take??

[Junky]

Reality check: the chances that someone will want to steal your code is extremely low.

[ozzyman]

Not steal code, copy software.

[Junky]

If you are so worried take out some Copywrite protection. But honestly it is a waste of time.

[ozzyman]

If you have nothing positive to contribute to this post, then please don't contribute at all. Firstly, you are making wild asumptions as to the value of someones 'code' which you have no clue what it is, and secondly, its not a waste of time and even if it was thats besides the point. Although you may think this isn't an important issue, it obviously is and thats why every product you buy requires activation.

[Junky]

Firstly you have no control over what I say. If you don't like it don't read it or leave. No skin of my nose. Secondly I don't have to make wild assumptions about your code. I highly doubt you have produced commercial grade software such as a word processor, spreadsheet etc that anyone would be interested in. So you are getting your panties in a knot over a very insignificant issue.

[ozzyman]

Once again, whatever I may or may have not produced is besides the point. Now you're just flaming for no reason whatsoever. All i'm asking is good methods to protect your software. You obviously don't have any so why waste your time posting here. Its not going to stop me from looking for good ideas.

[ozzyman]

And i'm not the one getting my panties in a knot!! Its clearly you :)

[Junky]

You were the first to get all defensive and tell me to mind my own business. Besides I go commando! :p

[ozzyman]

I wasn't being defensive, but you were being rude and patronising.

[Fubarable]

Regardless, what he states is true. You're concern is a non-issue. Better to spend your time worrying about quality of code and bug-proof code, then wasting time protecting code that no one will want to steal. And I'm not putting you or your quality of code as I consider you on par with me, it's just not likely to really be a serious concern. If someone truly wants your code, they will get it regardless of what "protection" you do.

[Junky]

you are making wild asumptions as to the value of someones 'code' which you have no clue what it is.

If that is not being defensive I'll go 'he'. Once again if you don't like what I have to say stop reading and/or replying.

[ozzyman]

I stand by that comment, if "probably" and "i doubt" aren't asumptions then I wonder what you make of them.

[aianta]

I'm not expert in Java programming, (still a major newbie but learning) but as far as protecting your code, the most efficient way that I have seen implemented by both large companies and independents is a system where you have each user connect to a server where the server checks the user as well as certain file in the software to detect "cracks".

Note however that this system tends to annoy users a lot since then need to be hooked up to the internet to use your software.

Also note that this method most likely require some hardcore programming to implement.

[ozzyman]

Thanks aianta for an excellent contribution. I also thought about those and thought the main downfall is the requirement of an internet connection. I then thought about how in the UK the digital satellite box companies require you to connect your box via the phone line, and was hoping that someone had more knowledge to share of that method. Everyone has a phone line!


Also, i'm not an expert either but I don't think it would require a lot of hard code to implement something to detect cracks. You'd probably just need to check the file attributes and make sure the size is correct, the file wasn't modified after some certain date, all the files are there etc

[ra4king]

How about have the program itself check for the file, instead of an online server? ;)

[Tolls]

Sell a service, not software.

[pbrockway2]

Have we stopped being controversial? Anyway, this from the original post:

So it would be nice if everyone shared their ideas.

I agree. And I regard that sentiment as a stake to be driven through the heart of the copyright zombie at every opportunity.

[JosAH]

For me, properly branding the software is enough; my software is not a high volume package (it controls highly dedicated hardware in very filthy factories and goes *beep* when some measured data goes out of range), but just putting in the name of the company that bought my software is enough to keep it from copying; and if they copy it, it's free advertising, the copier comes back to me a little later because they want additions to the software or some other little tweaks ...

It's is rather easy to change that name but until now nobody has done it (as far as I know). Most important is, those copiers are on their own, no service, no updates, no nothing from me ...

kind regards,

Jos

[ozzyman]

Tolls: I think if you go only for a service and not the software then you cut out a big chunk of your market, so its ideal to do both.

JosAh: That's also very true, but isn't it much easier when you're only providing a specialised software and/or in person? I'm also developing a semi-specialised software, and I'm not worried about selling it to the small businesses I plan on selling it to, because they have much more important things to do than copy and distibute my software. The problem is when, at the same time, you want your software to be able to be downloaded en masse on the internet for a small fee.

The biggest problem i'm facing right now is that my executable JAR file is ready to use - so no installation is required - just double-click it. How do I stop anyone from right-clicking, copy + paste :S. I mean I can't stop them from copy + paste. But I wouldn't like the program to work just by doing that.