[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 dkocher):

 Replying to [comment:12 bretmartin]:
 > Replying to [comment:9 dkocher]:
 > > Regardless of this we always defer the owner for the ACL we apply from
 the bucket and not from any existing owner of the ACL on the file. This is
 possibly the bug you describe.
 >
 > Yes, this sounds like it.
 >
 > Thanks for the change. I will test as soon as it appears in a snapshot
 build.

 The latest snapshot builds include this changeset. Can you confirm this is
 resolved?

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