mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[PR #1681] [MERGED] Set CURLOPT_UNRESTRICTED_AUTH when authenticating #2112
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2112
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1681
Author: @jstastny
Created: 6/14/2021
Status: ✅ Merged
Merged: 6/25/2021
Merged by: @ggtakec
Base:
master← Head:js/curl-redirect-auth📝 Commits (3)
848f657Set CURLOPT_UNRESTRICTED_AUTH when authenticating8b77821Merge branch 'master' into js/curl-redirect-auth94e995cMerge branch 'master' into js/curl-redirect-auth📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
src/curl.cpp(+1 -0)📄 Description
This is necessary for authentication to work with AWS when it responds with 307 to the check bucket request when mounting. This happens to newly created buckets according to https://aws.amazon.com/premiumsupport/knowledge-center/s3-http-307-response/.
Relevant Issue (if applicable)
N/A
Details
Prior to this, curl would follow the redirect, but would not include the
Authorizationheader which would end up with404.This is related to the change in cURL
7.58.0, where cURL stopped propagating theAuthorizationheader to redirects by default as mitigation of this CVE https://curl.se/docs/CVE-2018-1000007.html🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.