News for hackers. Stuff that matters.
Re:Linode hacked, CCs and passwords leaked by thaumaturgy on Monday April 15, 2013 @07:02PM (#5555063)
Linode hasn't been very forthcoming in the past where security "incidents" are concerned:

http://arstechnica.com/business/2012/03/bitcoins-worth-22800...

http://forum.linode.com/viewtopic.php?f=20&t=8509

I had really hoped that they had changed their stance on incident management. If it's true that they suppressed information about a possible wide-scale compromise where customer data could have been affected, then despite everything else about their service that's so great, there's no way anyone should want to continue to be a customer there.

Given Linode's past behavior and the information provided in the IRC chat, I think there's reasonable suspicion that customers' password hashes were stolen and Linode wasn't completely honest in their recent email to customers.

Re:Linode hacked, CCs and passwords leaked by taylorbuley on Monday April 15, 2013 @07:07PM (#5555089)
Did you see http://www.linode.com/linode4.css and http://www.linode.com/linode3.css?

Nevermind the security concerns. These guys aren't using version control!

Re:Linode hacked, CCs and passwords leaked by douglasheriot on Tuesday April 16, 2013 @11:21AM (#5558628)
Renaming CSS files with numbers or whatever is one legitimate way to handle cache invalidation (not evidence of not using version control)
Re:Linode hacked, CCs and passwords leaked by laxk on Tuesday April 16, 2013 @01:56PM (#5559668)
It is not the best way to handle cache invalidation. Why not /linode.css?v=<file_timestamp> ?
Re:Linode hacked, CCs and passwords leaked by thaumaturgy on Wednesday April 17, 2013 @12:47AM (#5562743)
This is inconsequential.