[Cyberduck-trac] [Cyberduck] #9007: New Folder with AES256 encryption

[Cyberduck]

#9007: New Folder with AES256 encryption
------------------------+-------------------------------
    Reporter:  mschaff  |      Owner:
        Type:  defect   |     Status:  new
    Priority:  normal   |  Milestone:  4.8
   Component:  core     |    Version:
    Severity:  normal   |   Keywords:  AES256 New Folder
Architecture:  Intel    |   Platform:  Mac OS X 10.10
------------------------+-------------------------------
 I have an AWS S3 bucket that enforces AES server-side encryption for all
 data.  Cyberduck data transfers work fine with the encryption flag set,
 but trying to create a New Folder fails with an "Access Denied" error.

 Using Amazon's console I could successfully create a new folder, so I
 compared the http headers to a folder created by Cyberduck in another
 bucket that doesn't enforce AES encryption.  The only obvious difference
 is that the folder created with Amazon's tool has the "x-amz-server-side-
 encryption: AES256" header set while the Cyberduck-created folder does
 not.  Can Cyberduck enforce setting this header when creating New Folders
 while AES256 encryption is enabled?

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