3 ms·
You're wrong. If I routinely share my lunch with someone at work, I don't get to poison it because "It's my sandwich, I'm under no obligation to make sure it's
by starwind 5y ago
You're wrong. If I routinely share my lunch with someone at work, I don't get to poison it because "It's my sandwich, I'm under no obligation to make sure it's safe just because you happen to eat it." Hell, I can't poison it even if someone's stealing my lunch.
I can't create code with malware. I can't modify my code to make it malware. That's a crime. You're wrong
- z3ncyberpunk 5y agoEverything about your comment is wrong. For one you're not giving your lunch to anyone, More analogously you're putting something in the refrigerator, and people can take at their own leisure and risk. You can poison it if you want, in fact it's a pretty common workplace tactic for people to mix in something like a laxative to THEIR OWN food because they're tired of it being stolen everyday. Again you make the choice to use the software, or take the food, the risk is on your head. And the cybersecurity industry would like to have a word with you since you don't believe it's possible to create malware.
- starwind 5y agoYou're wrong. You literally just described assault or (best case scenario) a tort https://law.stackexchange.com/questions/966/can-one-be-liable-for-poisoning-food-one-expects-to-be-stolen https://law.stackexchange.com/questions/966/can-one-be-liabl... > I can't create code with malware. I can't modify my code to make it malware. I guess I can appreciate your confusion but I still think I was clear in my previous comment. I'm willing to concede I would have been more clear if I had written: I can't legally create code with malware to distribute without a warning. I can't legally modify my code to make it malware if I know people are using it. PS I'm not discussing this further