Timeline for Should you notify software vendors that their software has been cracked?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2015 at 23:06 | answer | added | Steve Sether | timeline score: 2 | |
| Feb 9, 2015 at 18:22 | answer | added | Damian Nikodem | timeline score: 1 | |
| Feb 9, 2015 at 9:03 | history | edited | AviD♦ |
edited tags
|
|
| Feb 23, 2014 at 15:47 | comment | added | BrutalDev | @paj28: I think it definitely helps mitigate it but will never prevent it (I hope so for my own sake). But you're right, once a crack becomes available then it really doesn't matter how hard you've tried to keep people out. If you have the energy you can constantly make alterations and detect cracks so that each version becomes that much more difficult to circumvent. For a $20 app it's not worth the time, but for a $10000 app that is more than likely quite targeted, I would try an make the effort. | |
| Feb 23, 2014 at 15:33 | vote | accept | BrutalDev | ||
| Feb 23, 2014 at 12:46 | answer | added | Philipp | timeline score: 1 | |
| Feb 23, 2014 at 12:22 | comment | added | paj28 | @BrutalDev - will it really make a difference? If someone with your skills (but not your ethics) distributes a crack then it becomes very easy for anyone to just download and use that. Can vendors realistically increase the difficulty to the point that no-one will produce a crack? | |
| Feb 23, 2014 at 11:49 | comment | added | BrutalDev | @paj28: I would get no benefit from reporting it other than trying to help fellow software developers from potentially getting ripped off or losing sales due to piracy. Sure it will never be perfect but there are often small steps that can be taken to make it significantly more difficult to circumvent. The unfortunate reality is that you'll never be able to stop crackers altogether, but if the effort outweighs the cost then you've largely won the battle. A lot of time I wonder why the software isn't just free because it's far too easy crack. | |
| Feb 23, 2014 at 8:16 | comment | added | paj28 | What benefit would they get from your report? Anti-cracking systems are never perfect, and they already know that. Sure they could add some sticky tape which would stop the particular crack you created. But you could then just make your crack a bit smarter and it would work again. | |
| Feb 23, 2014 at 7:44 | answer | added | Matrix | timeline score: -1 | |
| Feb 22, 2014 at 23:18 | comment | added | user25787 | Many EULAs prohibit reverse engineering altogether. By telling them that you cracked their software, you're already at risk of a potential Breach of Contract suit... | |
| Feb 22, 2014 at 22:43 | comment | added | BrutalDev | @YolandaRuiz: Reporting anonymously is good, but trying to hide your identity creates suspicion which could backfire in itself. It seems like being a good Samaritan is just too risky :( | |
| Feb 22, 2014 at 22:23 | answer | added | ack__ | timeline score: 1 | |
| Feb 22, 2014 at 22:15 | history | tweeted | twitter.com/#!/StackSecurity/status/437349935600914432 | ||
| Feb 22, 2014 at 22:07 | comment | added | Yolanda Ruiz | I'd do it anonymously. Some people react in strange ways when confronted with flaws, and take it personally. There are examples where similar unsolicited constructive criticism actually backfired. | |
| Feb 22, 2014 at 21:48 | review | First posts | |||
| Feb 22, 2014 at 23:06 | |||||
| Feb 22, 2014 at 21:29 | history | asked | BrutalDev | CC BY-SA 3.0 |