126 karma · joined August 30, 2012
[ my public key: https://keybase.io/juanrossi; my proof: https://keybase.io/juanrossi/sigs/qSFT4hmTUstKrvX2mIBMjPWoQy61NDQfSG5dJJQ_j78 ]
Being from outside the US, it's hard to start a company there and create a bank account without spending thousands of dollars to travel there.
He could have sold all his shares before the IPO, but thought it was weird.
[1] https://www.sec.gov/Archives/edgar/data/1288847/000119312514...
Most of the cases was because of old CMS versions, but in same others the computer uploading the files was infected and the FTP credentials were stolen (Change your user/password and analyze ftp logs).
I would also check the database and do a clean install of the CMS.
The server could be compromised but I don't think this is the case.
EDIT: Wow, got a response in less than 5 minutes:
It's not something I'm looking at doing right now. The way the Tarsnap server side is designed, in order to keep costs low (and performance high), data is aggregated between multiple Tarsnap users and stored in S3 as large chunks; keeping each user's data segregated would add a lot of additional complexity and cost.
Design is Job - Mike Monteiro by A Book Apart (Really basic stuff for people starting with agency/freelance work, but really good).
Learn Ruby The Hard Way for people starting.
Applied Cryptography, Second Edition: Protocols, Algorithms, and Source Code in C
Baked In from Alex Bogusky and John Winsor (About C+P agency)
I'll try to think of a couple more.