Will Ashton wrote:
The main problem of this approach is, that the jar could be copied before it is launched the first time, because it needs to configure in the first start of the program.
Will Ashton wrote:Does anybody have a solution for this problem
or an alternative approach to copy-protection?
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Will Ashton wrote:Hm, dont get me wrong: I didnt ask for some unhackable and perfect protection, just about something that will hinder EVERY customer to freely distribute my software. To give some more details: we are talking about a game, that wont cost more than 5 bucks. I want to create an obstacle, which would make people think: "Hm, I could crack the protection and copy this software, but hey, its just 5$ so I wont do it, because its not worth the price".
Will Ashton wrote:I didnt ask for some unhackable and perfect protection, just about something that will hinder EVERY customer to freely distribute my software. To give some more details: we are talking about a game, that wont cost more than 5 bucks. I want to create an obstacle, which would make people think: "Hm, I could crack the protection and copy this software, but hey, its just 5$ so I wont do it, because its not worth the price".
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Will Ashton wrote:For this reason I want to write my code in a way, that it is safely distributable from the very first.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Ulf Dittmer wrote:I don't think there's anything wrong with considering how to protect my code before I write it, and I certainly don't see it as just an deployment issue. It might turn out to be one, but it could also have implications on how I write the code, so the sooner that is considered, the better.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Ulf Dittmer wrote:Security needs to be considered from the start, trying to bake it in afterwards generally produces less than optimal outcomes in my experience. It's a feature, and should be considered as such along with other features, as it may well have an impact on the design.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Ulf Dittmer wrote:Yup, we agree to disagree on this :-)
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Don't get me started about those stupid light bulbs. |