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

Change default ACL to inherit #5711

Closed
cyberduck opened this issue Feb 19, 2011 · 5 comments
Closed

Change default ACL to inherit #5711

cyberduck opened this issue Feb 19, 2011 · 5 comments
Assignees
@dkocher
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Milestone
4.4

Comments

@cyberduck
Copy link
Collaborator

9bd3466 created the issue

According to the Default ACLs in Cyberducks FAQ, if you have a default ACL specified in preferences, it will be applied to all uploaded files. However, if you turn this feature OFF, aka. uncheck the box "Change Permissions" under Preferenes >> Transfers tab >> Permissions tab >> Uploads section >> Change Permissions, the ACL that is applied is [Owner: FULL_CONTROL] only.

This behavior has been confirmed on 3.8 and current nightly build.

Private CloudFront distributions require special access, including a custom ACL. I would argue the better way would be to have the default be to apply an inherited ACL when the box is unchecked. This would eliminate the need to add a new user to the affected files after every upload.

Additionally, the functionality of forcing the upload to have [Owner: FULL_CONTROL] only would still be intact by enabling that checkbox and customizing the permissions.

On a side note, we use your software every day at work -- great stuff! Thank you so much!
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [5711 Decker Jesse]:

Private CloudFront distributions require special access, including a custom ACL. I would argue the better way would be to have the default be to apply an inherited ACL when the box is unchecked. This would eliminate the need to add a new user to the affected files after every upload.

Do you suggest the ACL should be inherited from the bucket?

@cyberduck
Copy link
Collaborator Author

9bd3466 commented

Replying to [comment:2 dkocher]:

Do you suggest the ACL should be inherited from the bucket?

Yessir. Thanks for clarifying.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 Decker Jesse]:

Replying to [comment:2 dkocher]:

Do you suggest the ACL should be inherited from the bucket?

Yessir. Thanks for clarifying.

The issue here is that the semantics for ACLs on the bucket are not the same for the same ACL on a object in the bucket. Not sure if such a policy to copy the ACL from the bucket would always lead to the desired result.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Wouldn't it be possible for this use case to apply a bucket policy? Refer to Granting Permission, Using Canonical ID, to a CloudFront Origin Identify.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 1dc3d8d. The ACL is only explicitly set if Change Permissions is checked in Preferences → Upload.

@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.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck