Multipart uploads do not retain ACL

[jabeler]

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.

[Chrispark7]

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.

[dkocher]

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.

[dkocher]

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

[dkocher]

The latest snapshot builds do no longer retain existing ACLs.