[Cyberduck-trac] [Cyberduck] #9322: S3 ACLs can't be changed in third-party buckets (due to incorrect Owner specification?)

[Cyberduck]

#9322: S3 ACLs can't be changed in third-party buckets (due to incorrect Owner
specification?)
------------------------+------------------------------
 Reporter:  bretmartin  |         Owner:  dkocher
     Type:  defect      |        Status:  closed
 Priority:  normal      |     Milestone:  5.0
Component:  s3          |       Version:  Nightly Build
 Severity:  normal      |    Resolution:  fixed
 Keywords:              |  Architecture:
 Platform:              |
------------------------+------------------------------

Comment (by bretmartin):

 Replying to [comment:8 dkocher]:
 > When trying to read the existing ACL on the file `test.txt` in the
 bucket we get a `403`  permission failure.

 This is expected -- I left the ACL on that object as set after upload by
 the third party IAM user. Because of the bug, that user couldn't change it
 afterward. Sorry for the confusion; I wasn't intending that you'd be able
 to change that object's ACL.

 > Therefore when updating the ACL where the `Owner` element must always be
 set the best thing to do is to use the known owner from the bucket.

 I agree that is a reasonable default. However, my proposal for you to
 reproduce my problem would have been for you to upload another object
 yourself, say `test2.txt`, and try to change '''its''' ACL. Since you
 would own it, you'd be able to retrieve its ACL as well.

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/9322#comment:11>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows