Re: encrypted source file support in jdk?
- From: tom forsmo <spam@xxxxxxxxxx>
- Date: Fri, 28 Sep 2007 11:41:05 +0200
Roedy Green wrote:
On Fri, 28 Sep 2007 08:42:41 +0200, tom forsmo <spam@xxxxxxxxxx>
wrote, quoted or indirectly quoted someone who said :
Try a little more open minded thinking next time you ask questions, dont just assume the person you are talking to is asswipe.
Quite often people want to spend huge amounts protecting software that
nobody wants to pirate. They think it is just the thing to do. There
are legal remedies as well.
First of all, when you create something you hope it will be of interest to others. So the only resonable thing to do is to protect it as best you can (unless its an open source project). If you create something that is going into a market with f.ex. intense competition and you are certain that BigDollars are going to notice and perhaps copy, then legal remedies does not help you. since the legal system is slow and by the time its finished there, they might have copied all your ideas, bundled it with their systems and marketing plans, made you spend so much money on legal stuff that you are unable to actually do something in the market or even develop the product furhter. And by the time the case is over, they have 100 million customers using their solution while you are broke and the company has next to no market share.
To explain again, what I am looking for is a way to protect the SOURCE CODE and CLASS FILES during DEVELOPMENT, that means only when the code is in-house. I am not talking about protecting class files distributed to the public.
It could perhaps be of interrest to protect the class files, but thats only relevant if I am the only one with access to the class files, for example when of I provide a web service where the class files are never distributed to the public.
Usually all you want is just to make it more expensive to crack your
code than compose it from scratch. The problem is, even with native
compilation, all you can do is slow down a determined hacker. After
all, the CPU has to crack the code to run it, so in principle all the
information needed is also available to the hacker.
To block brute force attacks you pretty well have to make the program
mutate and get fresh information frequently from the net, information
the hacker does not have in advance.
I dont agree that just because you cant get 100% security, you should abstain from any security.
regards
tom
.
- Follow-Ups:
- Re: encrypted source file support in jdk?
- From: Roedy Green
- Re: encrypted source file support in jdk?
- From: Thomas Schodt
- Re: encrypted source file support in jdk?
- From: Gordon Beaton
- Re: encrypted source file support in jdk?
- References:
- encrypted source file support in jdk?
- From: Tom Forsmo
- Re: encrypted source file support in jdk?
- From: rossum
- Re: encrypted source file support in jdk?
- From: tom forsmo
- Re: encrypted source file support in jdk?
- From: Roedy Green
- encrypted source file support in jdk?
- Prev by Date: Re: cannot load image
- Next by Date: image loading problem in login page
- Previous by thread: Re: encrypted source file support in jdk?
- Next by thread: Re: encrypted source file support in jdk?
- Index(es):
Relevant Pages
|
|