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

Renaming file fails when reading access control list #8750

Closed
cyberduck opened this issue Apr 16, 2015 · 5 comments
Closed

Renaming file fails when reading access control list #8750

cyberduck opened this issue Apr 16, 2015 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 16, 2015

8127343 created the issue

I have an s3 bucket that allows all permissions to the bucket.
It requires Server Side Encryption (SSE) to be turned on in the options of Cyberduck.
If you try to rename a file it fails.
However if I use Cloudberry's Explorer for S3 using same credentials with SSE turned on in Cloudberry app I am able to rename files.

This seems to be a bug in Cyberduck

I am using Cyberduck version: v. 4.6.5. (17000)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 16, 2015

@dkocher commented

Please post the transcript from the log drawer (⌘-L).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 16, 2015

8127343 commented

I removed the reference to the URL/S3 Bucket in transcript, I also removed Access key and Secret key info from transcript. Don't want to place that info public.
Of note though, you will see a line below that calls out that the secret key was different than the rest. I noticed this as I was removing that information from transcript.

GET /webinar%2Ftest_file_03.txt?acl HTTP/1.1
Date: Thu, 16 Apr 2015 17:31:14 GMT
Authorization: AWS (Removed Access Key & Secret Key)
Host: download.(Removed Website).com.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.6.5 (17000) (Windows 7/6.1) (x86)
GET /webinar%2Ftest_file_03.txt?acl HTTP/1.1
Date: Thu, 16 Apr 2015 17:31:14 GMT
Authorization: AWS (Removed Access Key & Secret Key)
Host: download.(Removed Website).com.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.6.5 (17000) (Windows 7/6.1) (x86)
HTTP/1.1 404 Not Found
x-amz-request-id: ACE9D2908DED2C95
x-amz-id-2: eT/8WZGeu3zhT9EtSSjM+D1IKKMp7rJkmX2bq16TBRqHWrdIxofVSuoW8HJD0XEOFGBSZGT/Dc8=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Thu, 16 Apr 2015 17:31:28 GMT
Server: AmazonS3
GET /?delimiter=%2F&max-keys=1000&prefix=webinar%2F HTTP/1.1
Date: Thu, 16 Apr 2015 17:31:31 GMT
Authorization: AWS (Removed Access Key & Secret Key)_ * Note of difference -Access Key on this line was same as others, HOWEVER secret Key was different._
Host: download.(Removed Website).com.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.6.5 (17000) (Windows 7/6.1) (x86)
HTTP/1.1 200 OK
x-amz-id-2: sR+XGaKbtgxKLWGXCLJsuaDQV0vyoBW4OiV7Wor1dEKxl1yB7PmIOY+60SSirt+NXz8Inn8XSE4=
x-amz-request-id: 557A92AEFEA919D6
Date: Thu, 16 Apr 2015 17:31:32 GMT
Content-Type: application/xml
Transfer-Encoding: chunked
Server: AmazonS3

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2015

@dkocher commented

The different authorization header is expected as it is derived from the access credentials.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2015

@dkocher commented

Added test in fc78626. We cannot reproduce this issue. What is the error message displayed?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2015

@dkocher commented

Please make sure you have READ_ACP or FULL_CONTROL permission for the object to move.

Loading

@cyberduck cyberduck closed this Apr 17, 2015
@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