Timeline for Is it legal/ethical to release commercial software with known security flaws
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2017 at 21:31 | comment | added | dark_st3alth | Very well detailed, should be the accepted answer. | |
| Jan 10, 2017 at 21:00 | comment | added | Peteris | Shipping a known defect is strictly different than injecting a vulnerability on purpose - in both cases it's the same code put in by the same people, but the intent is different, and intent is a major deciding factor in law. You can definitely claim that they did put there on purpose, but I would be quite surprised if that would be accepted in court without some specific evidence showing intent. And yes, I definitely am claiming that shipping a known security flaw is exactly the same as shipping a serious known flaw of some other kind. | |
| Jan 10, 2017 at 20:51 | comment | added | Ubaidah | The question is not about releasing software with a bug. Almost all software companies do that. Let us say that as I client I discover this vulnerability and decide to start a lawsuit against the company. I will also claim that they injected this vulnerability on purpose. Since they already know, it exists. In other words, it is a malicious code that they put. | |
| Jan 10, 2017 at 20:35 | history | edited | Peteris | CC BY-SA 3.0 |
added 307 characters in body
|
| Jan 10, 2017 at 20:29 | history | answered | Peteris | CC BY-SA 3.0 |