\[REPORT\] DigitalOcean leaks customer data between VMs
-
[url=https://github.com/fog/fog/issues/2525]https://github.com/fog/fog/issues/2525[/url]
Reply …
[url=https://www.digitalocean.com/blog_posts/transparency-regarding-data-security]https://www.digitalocean.com/blog_posts/transparency-regarding-data-security[/url] -
This is a good example of how to run a VPS host: With transparency.
The discussion got going on Twitter, then moved to github, where they became actively involved in the conversation. Before 24 hours had passed, an official stance on the issue was posted, a temporary fix was sanctioned, a timeline put in place for a permanent fix, and an apology issued to those who were affected where they took full responsibility for both the change that caused the problem in the first place, and not notifying people of the change via email.
I for one welcome our new cloud provider overlords.
(Full disclosure: I’m a paying digitalocean customer who had the potential to be impacted by this, but wasn’t)
-
I have to agree with Kevlar.
I’m a paying DigitalOcean customer, although this has not impacted me as I’ve not destroyed any droplets with any real data on them. I think the way they’ve handled it is good in that they’ve responded factually, apologised and are working on keeping the customers updated and aware.
FWIW, I’m very happy with their service and have had no issues with them over the year and a half I’ve been using their droplets. Linode is still my VPS provider of choice for my main production boxes, but for the price DigitalOcean cannot be beaten for demo/dev/backup VPS solutions IMHO.