-
Notifications
You must be signed in to change notification settings - Fork 181
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
Support for AWS signature version 4 #45
Comments
Maybe it's possible to solve this by making use of this https://github.com/mitchellh/goamz/blob/master/s3/sign.go |
I'd also appreciate if this bug (which it is, in my view) would get fixed. s3gof3r is a very nice tool and a real alternative to all the other S3 utilities, but not being able to connect to the Frankfurt region is a deal breaker for me. Obviously, Amazon will at some point turn off the older signatures anyway, so implementing AWS4-HMAC-SHA256 support would have value in its own right, in my opinion. |
@rlmcpherson is this planned anytime? This is a bug, as it totally doesn't work for Frankfurt. Would you accept a PR? |
Same question here, I use Frankfurt buckets so I cannot go with s3gof3r for now.. |
@ukd1 Yes, pull requests are always welcome! |
#74 aims to fix this. |
Fixed by #74. Thanks @cyberdelia! |
All regions created after January 30, 2014 (e.g. Frankfurt) support only signature version 4. http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
The text was updated successfully, but these errors were encountered: