[thehermit]

The chatlog does provide some evidence that it is indeed the hacker, but does little to convince me that he got CC info and Linode is not telling us the whole truth. The evidence he provides is just simple source code snips and the directory listing, which would be expected based on what Linode has told us.

This could very well be the hackers own submission to /. trying to get more attention for his hack by claiming he has CC numbers which I doubt he has.

[lawnchair_larry]

Doubting the claims of a hacker after it's known that they compromised a system is really bad OpSec. Consider everything burned.

[thehermit]

That's a fair point. I'm speaking more as a judge/jury view on the situation though. I don't think Linode users should panic and run for the hills just yet based off this alone.

[jdhore]

I know the /. submitter (As he's the one who told me he submitted it to /. and he had the first /. link I saw), he's definitely NOT the hacker.

[nenolod]

Except Linode didn't tell us that. Linode said it was a downstream customer's info that was compromised. Nothing about Linode itself.