Live data from Hacker News

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

ideas.digitalocean.com

21–30 of 104 posts

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

#23
post #22
post #21

Why the smaller players can't figure this out? Are they inventing their own S3-compatible storage or using a open source project underneath if?

They are all using Ceph, which is the limitation.

Is this true? That's horrifying

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

#26
Well, it used to be same for Cloudflare R2 , which was just fixed less than two months ago [1]. This was an unexpected showstopper for me.

I honestly find it hard to understand why this kind of basic security feature wasn't in GA.

[1]: https://community.cloudflare.com/t/r2-token-per-bucket/38906...

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

#27
post #22
post #21

Why the smaller players can't figure this out? Are they inventing their own S3-compatible storage or using a open source project underneath if?

They are all using Ceph, which is the limitation.

Do you mean Ceph Object gateway? I am not familiar with Ceph but does it have serious limitations?

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

#28
post #19
post #9

Earlier quoted context omitted.

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

Some of the comments by DO on that GitHub thread, are really surprising, and disappointing to say the least...

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?) instead of emailing us about it isn't a very responsible way to disclose it and, there isn't actually a security issue, the fog app wasn't passing the scrub flag. In retrospect, I should have been less of a jerk, but I still think sneak was acting in bad faith in how he went about the whole thing. 10 years later and I still remember how pissed off I was that day, hah.

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

#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 at least have an API key that can only access the DNS domains and nothing else. As is, the key can create compute resources or delete anything (including object storage buckets!). Again with no dev/prod isolation, so a leaked dev key that looks innocuous means your prod resources are now compromised.

Some second tier providers do better at this, OVH and scaleway both have some concept of ACLs, but DO just don't even try.

Apologies for the slight rant but it's frustrating to see something so basic overlooked by a company the size of DO.

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

#30
post #6

And DO consistently ignores requests to add this. It prevents me from seriously using Spaces and I think many others, too.

DO has had a terrible attitude to security for as long as they've been around. I reported a major data leak vulnerability to them and they told me it was operating as intended, so I published it, and then they accused me of irresponsible disclosure, while simultaneously claiming that there was no security issue. This was a dozen years ago and the founders were involved in the response. They are at the top of the list…

[dead]
Post reply on HN