The part where he gets contacted over the hit-and-run reads like the curl guy’s experience with people investigating “hacking”.

I wonder how often this happens outside of software? Do fence manufacturers get emails asking to identify the culprit when someone crashes through a fence?

▲

ikidd an hour ago | parent | next [-]

Actually, it wasn't unreasonable. If the guy caused the damage while picking up a sonde, to know who's sonde it was would help identify the culprit.

	▲	dlgeek 41 minutes ago \| parent \| next [-]
		Or maybe the sonde continued transmitting and they have data on where the guy took it which would help ID him.
	▲	iamnothere an hour ago \| parent \| prev [-]
		Fair, I guess, I just can’t imagine what it’s like getting all these weird requests and demands for a hobby project. Hopefully the author is more entertained than I would be.

▲

BowBun 2 hours ago | parent | prev | next [-]

I feel like it's a "cast a wide net" type of strategy. Doesn't really hurt to ask and there _could_ be the tiniest hint that could lead to something. Maybe?

	▲	genghisjahn an hour ago \| parent [-]
		In my first law class the prof said, "When it doubt, sue everybody."

▲

TZubiri 26 minutes ago | parent | prev [-]

Rings a bell, I think it was because Curl showed up as the user agent for malicious activity.

You have to be kind of lost to contact Daniel about it, but I think it's ok behaviour for junior sysadmins that are just starting out, everyone was starting out sometime, and curl is like a lightning catcher for the world's daily lucky thousand.

	▲	Arrowmaster 14 minutes ago \| parent [-]
		It's because curl is often embedded as a library or standalone executable with other software. So when a malicious or compromised piece of software is found, a less experienced investigator might see curl with its author tags in the file metadata, and follow it back to upstream.