News for hackers. Stuff that matters.

A comment on Defense Contractor Left Sensitive Pentagon Files on Unprotected AWS S3 Bucket. Parent comment

Re:Defense Contractor Left Sensitive Pentagon Files on Unpro... by conorh on Wednesday May 31, 2017 @01:07PM (#14454098)
We 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

[ Parent | on HN ]
Re:Defense Contractor Left Sensitive Pentagon Files on Unpro... by danso on Wednesday May 31, 2017 @02:12PM (#14454683)
Yeah, 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.
[ Parent | on HN ]
Re:Defense Contractor Left Sensitive Pentagon Files on Unpro... by jamiesonbecker on Wednesday May 31, 2017 @01:41PM (#14454418)
tinyS3 used to do this as well:

https://github.com/smore-inc/tinys3/issues/44

[ Parent | on HN ]