3 ms·

OK, let's be sensationalist for a moment: I should stop using Google, Dropbox, Microsoft, Apple, Sony, Amazon... They have all been hacked at one point or anot

by mjs7231 14y ago

OK, let's be sensationalist for a moment: I should stop using Google, Dropbox, Microsoft, Apple, Sony, Amazon... They have all been hacked at one point or another and very rarely do we get details of what actually happened. Ohh yea, I should give up my US citizenship as well. I hear about the US gov getting hacked all the time and they don't let us know whats going on either. People love hating on hosting companies, and touting their own horror or success stories. When will people realize that mistakes are inevitable. To me, one mistake every once in a while is forgivable. Perhaps I could also careless about bitcoins (they seem about as worthless as Second Life money). Linode did mention publicly that only 8 accounts were compromised and no credit card info or passwords were available to them.

freehunter 14y ago
Also, while I'm not commenting on Linode's response to the incident, ultimately the security of your information is up to you. The owner of the stolen Bitcoins has publicly stated that he learned a lesson: encrypt your data. Your server, your data, your information is only as safe as you make it. Even if everything is fully encrypted and all a hacker could do to mess with you is delete your instance, you should have offsite backups of your important stuff. Always assume you're going to lose everything. Whether it's hardware failure, hacking, or a simple mistake, treat a gun like it's loaded. Encrypt your important data. Use two-factor authentication on privileged accounts. If you want Bitcoins to be a currency, then read up on Payment Card Industry regulations and really understand how to keep a currency secure.Hire an auditor if need be. Everyone is going to be hacked, everyone is going to be embarrassed, and your data is never secure unless you make it secure.
- throwaway64 14y ago
  encrypting your data doesn't help when it is inside memory and somebody else has root. the attack was a hypervisor intrusion, linode's VM setup was hacked, none of these recommendations would have helped at all in this case.
  - freehunter 14y ago
    Linode does offer basic two-factor authentication, which was one of the things I mentioned. You have the ability to set up IP address whitelists. If you try to log in from an address not on the whitelist, you get an email to confirm you are who you say you are. If I know the attack correctly, the hacker reset (or otherwise gained) the password via the support console and used that to log in. With two-factor, he could get the right password but would still need access to the email account as well. Unless you've majorly fucked up, there is no way anyone besides you is getting root. You sign no SLA with Linode. They make no guarantees. That leaves it up to you to make sure you're secure, and fortunately they give you the tools needed to make this a reality.
- deleted 14y ago
  [deleted]

by mjs7231 14y ago

freehunter 14y ago

Also, while I'm not commenting on Linode's response to the incident, ultimately the security of your information is up to you. The owner of the stolen Bitcoins has publicly stated that he learned a lesson: encrypt your data. Your server, your data, your information is only as safe as you make it. Even if everything is fully encrypted and all a hacker could do to mess with you is delete your instance, you should have offsite backups of your important stuff. Always assume you're going to lose everything. Whether it's hardware failure, hacking, or a simple mistake, treat a gun like it's loaded. Encrypt your important data. Use two-factor authentication on privileged accounts. If you want Bitcoins to be a currency, then read up on Payment Card Industry regulations and really understand how to keep a currency secure.Hire an auditor if need be. Everyone is going to be hacked, everyone is going to be embarrassed, and your data is never secure unless you make it secure.

throwaway64 14y ago
encrypting your data doesn't help when it is inside memory and somebody else has root. the attack was a hypervisor intrusion, linode's VM setup was hacked, none of these recommendations would have helped at all in this case.
- freehunter 14y ago
  Linode does offer basic two-factor authentication, which was one of the things I mentioned. You have the ability to set up IP address whitelists. If you try to log in from an address not on the whitelist, you get an email to confirm you are who you say you are. If I know the attack correctly, the hacker reset (or otherwise gained) the password via the support console and used that to log in. With two-factor, he could get the right password but would still need access to the email account as well. Unless you've majorly fucked up, there is no way anyone besides you is getting root. You sign no SLA with Linode. They make no guarantees. That leaves it up to you to make sure you're secure, and fortunately they give you the tools needed to make this a reality.
deleted 14y ago
[deleted]