4 ms·
It's really confusing how they ended up in this predicament. S3 buckets are private by default. You have to manually configure them to be public-read. Given the
by danso 9y ago
It's really confusing how they ended up in this predicament. S3 buckets are private by default. You have to manually configure them to be public-read. Given the scope of Booz Allen's work, it doesn't seem like they needed any of the S3 buckets to ever be just public. I wonder if they're using software or maybe even just copied a script in which the default assumption for S3 configuration and uploads is to set files to be public?
- QuinnyPig 9y agoI'm wondering if they were bitten by the semi-common "any authenticated user" misunderstanding. That maps to any user in all of S3, not just your account.
- unclesaamm 9y agoMuch more likely for it to be the ole "Download it quickly and I'll make it private" Edit: After reading the article, I have no idea what could explain this. They had a dozen passwords in there as well..
- deleted 9y ago[deleted]
- conorh 9y agoWe had this issue previously as one of our clients was using cyberduck to upload files and it had default read access for public for uploads. [1] https://forums.aws.amazon.com/thread.jspa?messageID=213248 https://forums.aws.amazon.com/thread.jspa?messageID=213248
- jamiesonbecker 9y agotinyS3 used to do this as well: https://github.com/smore-inc/tinys3/issues/44 https://github.com/smore-inc/tinys3/issues/44
- danso 9y agoYeah, this is also something that can be set using Transmit (my OS X GUI of choice). I guess I assumed that, given the size of the data they have to manage, they have something more sophisticated than file-management-by-click-and-drag but...maybe I'm giving them too much credit in terms of dev ops.
- empath75 9y agoThis happens surprisingly often.
- Florin_Andrei 9y agoWho knows what dumb GUI they used that configures the bucket with public access by default.