Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

In Digital Ocean, S3-like space keys can access all your buckets

ideas.digitalocean.com

Post reply on HN
Print view View original

91–100 of 104 posts

Re: In Digital Ocean, S3-like space keys can access all your buckets

#91

Post by fullspectrumdev »

sneak wrote: post #9
mdekkers wrote: post #7

Earlier quoted context omitted.

Could you provide more details?

On delete of VMs, the next user to be allocated disk would be able to read your data. There was a "scrub" feature that would bill you longer/extra to zeroize your data and not give it to the next customer. Apparently they hadn't heard of TRIM or thin provisioning. https://github.com/fog/fog/issues/2525 https://news.ycombinator.com/item?id=6983097 https://news.ycombinator.com/item?id=6983520

Holy shit that’s bad.

I wonder how one could test for that “automatically” on other providers.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#92

Post by tigeroil »

turtles3 wrote: post #29

The lack of ACLs or comparable permissions is by far the biggest thing that prevents me from recommending DO for production workloads. This kind of thing is absolutely essential. You can't even separate dev resources from prod resources, every API key has godmode on your whole account. This is a security disaster. For a simple example, I'm running externaldns on a kubernetes cluster. For production use, I'd want to a…

You've described exactly why my company moved from DigitalOcean to AWS a while ago.

Whilst AWS is more expensive and perhaps over-engineered for our use-case, it was absolutely essential to have some kind of ACLs.

I mean, I can't exactly give my junior dev access to DO if it means he can also delete the entire production database and all backups with a misclick.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#93

Post by tigeroil »

kyledrake wrote: post #90

Aside from this, their Spaces service has had multiple outages, the service seems to be pretty unreliable in general (definitely compared to S3). A quick glance of their NYC3 status suggests they may have finally improved this recently, but I don't know what use case I would have for a version of S3 that goes down multiple times a year.

Indeed - I used to use Spaces for a project but found not just the uptime but teh overall reliability and performance was, at the time at least, markedly worse than AWS.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#94

Post by j45 »

DigitalOcean should not be used for production use, or the sole network.

There is a critical flaw in their operations management that will delete all of your long standing droplets with a valid credit card on file and zero issue with the conduct of the droplets or with the credit card.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#95

Post by j45 »

Another reason DigitalOcean should not be used for production use, or the sole network.

I am looking into blackblaze and other providers.

As seriously, Digital Ocean contains a critical flaw in their operations management that will delete all of your long standing droplets with a valid credit card on file and zero issue with the conduct of the droplets or with the credit card.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#96

Post by ratg13 »

neom wrote: post #87
ratg13 wrote: post #85

Earlier quoted context omitted.

I just told you in my previous comment.. In the event your google is broken: ---- https://en.wikipedia.org/wiki/Data_Protection_Directive > the controller must implement appropriate technical and organizational measures to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorized disclosure or access, in particular where the processing involves the transmission of d…

https://en.wikipedia.org/wiki/Personal_data

Are you confused about what PII is?

Should I explain this too?

Re: In Digital Ocean, S3-like space keys can access all your buckets

#97

Post by dang »

sergioisidoro wrote: post #2

S3 (and similar storages) have caused plenty of security issues in several occasions (usually because of misconfigured buckets, making all contents available to the public). Given this, it would be expected that companies would pay a bit more attention to the security of these data storage methods. However, in Digital Ocean, by design, you can't restrict keys to certain buckets. Once you issue a key, it can access al…

I'm afraid you broke the site guidelines by using the submission title to editorialize. Please see https://news.ycombinator.com/newsguidelines.html: "Please use the original title, unless it is misleading or linkbait; don't editorialize."

If you want to say what you think is important about a page, that's fine, but do it by adding a comment to the thread. Then your view will be on a level playing field with everyone else's: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so.... Alternatively, you could have made a text post to communicate what you think is important about the issue, and then your title would have been fine.

What's not ok on HN is to use the title field as a way to comment on an issue, because then the submitter gets a privileged position relative to other commenters. Since the title is by far the largest influence on a thread, we want to avoid that. Being the submitter of a page shouldn't confer any extra special power over the discussion.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#98

Post by fullspectrumdev »

plagiarist wrote: post #46
neom wrote: post #28

Earlier quoted context omitted.

I wrote those comments, fog wasn't using the API as he would have liked, and then this guy starts a bunch of trouble on HN stating that there was a vun on DigitalOcean, and conflated someone using the API incorrectly with us having a security vun. Two things I was trying to (admittedly not very well) say was: if DO did have a security issue, posting it on HN ("DigitalOcean leaks customer data between VMs" huh?) inste…

Why on Earth would someone have to opt-in to scrubbing with a flag vs. opting out? That's surprising. Is the flag on by default and they specifically opted out before complaining about it?

The scrub flag was default false, apparently because scrubbing was slow and caused wear.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#99

Post by jddj »

ph4te wrote: post #84

I used to use DO Spaces and Backblaze, but then I found Wasabi and have switched everything over since. It pretty much has full S3 compatibility, and doesn’t use Minio or Ceph. Mostly just keep adding data, very rarely delete data.

Same here, very happy with wasabi so far.

Re: In Digital Ocean, S3-like space keys can access all your buckets

#100

Post by slig »

mootline wrote: post #88

I unfortunately had to ditch DigitalOcean because of a number of small problems like this (not taking permissions seriously is a symptom of a larger problem). Other issues included how you can't assign a floating IP to a load balancer, the managed kubernetes is embarassing (to resize nodes, you must destroy and recreate the whole cluster), paltry volumes IOPS, minimal support for DNS stuff, and more.

AFAIK, you don't need to destroy the cluster and recreate it, just add the nodes you want and destroy the old ones.
Post reply on HN