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

Multipart uploads do not retain ACL #6491

Closed
cyberduck opened this issue Jan 21, 2012 · 4 comments
Closed

Multipart uploads do not retain ACL #6491

cyberduck opened this issue Jan 21, 2012 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 21, 2012

2602672 created the issue

When uploading certain file types (.zip, .deb, and possibly others) to S3, the permissions are set incorrectly.

For example, overwriting a specific file on S3 previously resulted the bucket/file permissions being carried over to the newly uploaded files. E.G.

Owner = read/write

Everyone = read

Now when uploading zip and deb files only the Owner permission is set, there is no entry for Everyone.

Uploading other files such as .plist, and .txt files result in the correct permissions for both Owner and Everyone.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 25, 2012

Chrispark7 commented

I can confirm this defect is also new in the windows version of the program, as well. However, it's not based on file type so far as I can tell -- it's based on file size. I'm not sure what the cutoff is, but if the file is smaller than a couple of megabytes then it will keep the permissions of the bucket (or the file that is being overwritten in that case). If the file is about 5mb or larger (for sure -- it may be an issue below that), then 100% of the time it will act as the reporter describes above.

This basically means that, for me, cyberduck is halfway uselses for Amazon S3, because I wind up having to log into the amazon console and set permissions after every upload above a certain size. This was not an issue in 4.1, but I missed a few versions and so I don't know exactly what new version this appeared in.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 25, 2012

@dkocher commented

This is less of an issue with the current snapshot build (and upcoming 4.2.2) as we have a much larger threshold for multipart uploads of 5GB.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 25, 2012

@dkocher commented

Instead of switching to the snapshot build, you could also change the threshold preference for multipart uploads with

defaults write ch.sudo.cyberduck s3.upload.multipart.threshold 5368709120

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 23, 2013

@dkocher commented

The latest snapshot builds do no longer retain existing ACLs.

Loading

@cyberduck cyberduck closed this Jul 23, 2013
@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
2 participants