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

S3 permissions for overwriten files #10036

Closed
cyberduck opened this issue Aug 2, 2017 · 2 comments
Closed

S3 permissions for overwriten files #10036

cyberduck opened this issue Aug 2, 2017 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 2, 2017

1f06990 created the issue

Hi

Not sure if it is a bug or a feature but if I replace a file in an S3 bucket it will loose it's ACL. I would really appreciate a way for CyberDuck put back the same ACL as the file being replaced.

At the moment Preferences → Transfers → Permissions → Upload → Change Permissions - Uploads Change Permissions is unchecked

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 1, 2017

@dkocher commented

Make sure the Change Permissions options is checked which will apply the ACLs of the file that is overwritten.

Loading

@cyberduck cyberduck closed this Nov 1, 2017
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 1, 2017

1f06990 commented

I have tried your suggestion and it seems to work - thanks.

That being said at the moment the UI suggest that Cyberduck will apply the uploaded file permission to match the one of the local file. I don't see how this would be useful (as there is no obvious mapping between the local and remote users) and I suggest to change the wording to "maintain whatever existing permission was set to the remote file being overwritten".

Loading

@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant