Re:Edited version of the Linode log file for April 15th
by scraplab on Tuesday April 23, 2013 @02:43AM
(#5593639)
The CEO has already stated that the private key had passphrase encryption, which is strong, and only stored in their heads. You have to take their word on that, but I don't see any proof of CCs being decrypted.
Re:Edited version of the Linode log file for April 15th
by err_badprocrast on Tuesday April 23, 2013 @03:04AM
(#5593701)
07:52 < HTP> the CCrypter class of the linode application
context was accessable from outside the wwwroot using
undocumented ColdFusion methods. i was fully able to
decrypt the ccs using the in-memory privkey that they
supplied the password for.
From the 2nd pastebin'd IRC log, http://pastebin.com/7WXRDyAgNote that he states all information was deleted. They had claimed earlier that CC info would be released on May 1st.
note: temp account because I accidentally set noprocrast delay to 1 week. Whoops!
Re:Edited version of the Linode log file for April 15th
by leeoniya on Tuesday April 23, 2013 @02:53AM
(#5593667)
i cannot imagine that a remembered passphrase would take too long to brute-force on a few multi-GPU setups. unless they did something meaningful like making it a long sentence rather than some short-but-complex-for-humans 15 char string. http://xkcd.com/936/
Re:Edited version of the Linode log file for April 15th
by eridius on Tuesday April 23, 2013 @04:27AM
(#5593953)
Specifically what they said is it isn't stored digitally. So maybe they have it written down on a piece of paper.
Re:Edited version of the Linode log file for April 15th
by threeseed on Tuesday April 23, 2013 @04:42AM
(#5593982)
Based on what we've seen before I wouldn't give Linode the benefit of the doubt.
The password is most likely cracked by now.
> 06:00 < ryann> Yep
> 06:00 < AlexC_> ryann: And you plan on releasing these?
> 06:00 < ryann> They did try to encrypt them, but using public key encryption doesn't work if you have the public and private key in the same directory
Jesus Christ. I agree, there is something very wrong with how Linode is treating this situation. Cperciva's comment a couple of days back about the doubletalk in the official statement seems especially precinct, and the new claim about both the private and public keys for the credit card info being stored in the same place... appallingly incompetent if true.