See also:

People finding the curl copyright notice in an application and blaming Daniel Stenberg for hacking them:

https://daniel.haxx.se/blog/2016/01/19/subject-urgent-warnin...

Or the reason sqlite no longer uses "sqlite" as a file extension for temporary files:

https://github.com/endlesssoftware/sqlite3/blob/master/os.h#...

Found this gem in the comments of the first one:

A city in Oklahoma threatened to call the FBI over an Apache error message... and sent the threat to CentOS.

https://www.theregister.com/2006/03/24/tuttle_centos/

The best part is the cities tuttle-ok.gov website has not come back online since 2006. They just gave up and built another website at cityoftuttle.com

I don't understand why CentOS, and Stenberg above, spend any energy engaging with these people.

> How about simply renaming curl to zurl so that you end up at the very bottom of the list and hand over the case to the next dependency in alphabetical order?

> Also, Spotify is a major partner of Spotify

Can't argue with that

This is great, thanks for posting.

Ha ha ha, surely not, it's too hilarious. Must be a top tier troll :)

They no longer use that as a file prefix, rather.

>#Stop scanning and probing our network, XXX.XX.X.X/16. We are a defense

#contractor and report to Federal law enforcement authorities when scans

#and probes are directed at our network. I assume you don't want to be

#part of that report. Please permanently remove our network range from

#your current and future research.

that one's amusing, but this one, in a git repo, is :chefs_kiss:

#NOTICE: This e-mail and any attachments is intended only for use by the add= #ressee(s) named herein and may contain legally privileged, proprietary or c= #onfidential information. If you are not the intended recipient of this e-ma= #il, you are hereby notified that any dissemination, distribution or copying= # of this email, and any attachments thereto, is strictly prohibited. If you= # receive this email in error please immediately notify me via reply email o= #r at (800) 927-9800 and permanently delete the original copy and any copy o= #f any e-mail, and any printout.

Maybe we should call them, to say we "averted our eyes, m'lord"?

So di@egihosting posted a list of all their public ip addresses, this seems like it would help an intruder more than the port scanning??

Yes, this list seems like a catalogue of easy targets more than anything else.

Do we need a ROT13 encryption for Dev Names and emails?

I think that if people are upset their name is up on a list clearly meant to shame them for being stupid, then contacting the author to say "ok I understand now, can you please remove us from that list" will definitely get them removed.

But I suspect if someone is the kind of person to email a tool author because of what an unrelated tool user is doing, they're probably going to be quite chuffed there's a tangible outcome they can point at and say "see, I fixed the issue"