Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Default bucket ACL #6162

Closed
cyberduck opened this issue Aug 22, 2011 · 4 comments
Closed

Default bucket ACL #6162

cyberduck opened this issue Aug 22, 2011 · 4 comments
Assignees
@dkocher
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Milestone
4.1.2

Comments

@cyberduck
Copy link
Collaborator

feb6e03 created the issue

Under the S3 preferences it would be great if we could set a default ACL for bucket/file/folder creation, by default cyberduck gives the owner full access and everyone else read access, since I never create public buckets I have to remove the everyone bit for each creation which can lead to some buckets remaining public due to human error.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Hidden configuration option s3.bucket.acl.default in bd8b2b8. Will possibly introduce a graphical option in the preferences later.

@cyberduck
Copy link
Collaborator Author

feb6e03 commented

I just tried that option and verified it is set in the plist file but it doesn't work any new buckets I create still have "Everyone" set to read access.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Now documented in the wiki.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 http://rwky.pip.verisignlabs.com/]:

I just tried that option and verified it is set in the plist file but it doesn't work any new buckets I create still have "Everyone" set to read access.

You will need a snapshot build later than bd8b2b8 to be available later today.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.1.2
Development

No branches or pull requests
2 participants
@dkocher @cyberduck