←back to thread

742 points janpio | 5 comments | | HN request time: 0.409s | source
Show context
jdsully ◴[] No.45677260[source]
The one thing I never understood about these warnings is how they don't run afoul of libel laws. They are directly calling you a scammer and "attacker". The same for Microsoft with their unknown executables.

They used to be more generic saying "We don't know if its safe" but now they are quite assertive at stating you are indeed an attacker.

replies(4): >>45677490 #>>45677615 #>>45678221 #>>45678896 #
1. pasteldream ◴[] No.45677490[source]
> The one thing I never understood about these warnings is how they don't run afoul of libel laws.

I’m not a lawyer, but this hasn’t ever been taken to court, has it? It might qualify as libel.

replies(2): >>45677851 #>>45678158 #
2. altairprime ◴[] No.45677851[source]
I know of no such cases, and would love to know if someone finds one.
replies(1): >>45678457 #
3. modzu ◴[] No.45678158[source]
you only sue somebody poorer than you
replies(1): >>45679182 #
4. trenchpilgrim ◴[] No.45678457[source]
I worked for a company who had this happen to an internal development domain, not exposed to the public internet. (We were doing security research on our own software, so we had a pentest payload hosted on one of those domains as part of a reproduction case for a vulnerability we were developing a fix for.)

Our lawyers spoke to Google's lawyers privately, and our domains got added to a whitelist at Google.

5. tgsovlerkhgsel ◴[] No.45679182[source]
It depends, if it's a clear-cut case, then in jurisdictions with a functioning legal system it can be feasible to sue.

Likewise, if it's a fuckup that just needs to be put in front of someone who cares, a lawsuit is actually a surprisingly effective way of doing that. This moves your problem from "annoying customer support interaction that's best dealt with by stonewalling" into "legal says we HAVE to fix this".