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.

Sign up for GitHub

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

Setting acl to private doesn't revoke public-write acl #1151

Closed
orztt opened this issue Nov 17, 2020 · 2 comments
Closed

Setting acl to private doesn't revoke public-write acl #1151

orztt opened this issue Nov 17, 2020 · 2 comments
Milestone
2.2.0

Comments

@orztt
Copy link
Contributor

orztt commented Nov 17, 2020

There is object whoes ACL is public-read-write, which i used awscli setting.
Then i used s3cmd setacl s3://object --acl-private to set object acl to private. However, the object'acls still have ACL: *anon*: WRITE item.
I can understand s3cmd only provides "acl-public", not "acl-public-read-write" for safety reasons. But i think "acl-private" should be consistent with awscli.
So, i think s3cmd setacl s3://objetct --acl-private should revoke ACL: *anon*: WRITE item.
@orztt orztt mentioned this issue Nov 17, 2020
Merged
@orztt
Copy link
Contributor Author

orztt commented Nov 17, 2020 •
edited
Loading

there is my fix: #1152

@fviard fviard added this to the 2.2.0 milestone Dec 14, 2020
@fviard
Copy link
Contributor

fviard commented Dec 14, 2020

Good idea, your PR was merged.

@fviard fviard closed this as completed Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.2.0
Development

No branches or pull requests
2 participants
@fviard @orztt