mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #882] [MERGED] [curl] Assume long encryption keys are base64 encoded #1672
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#1672
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/882
Author: @earlchew
Created: 1/5/2019
Status: ✅ Merged
Merged: 1/6/2019
Merged by: @ggtakec
Base:
master← Head:issue-817📝 Commits (2)
41c23ad[curl] Assume long encryption keys are base64 encodeded5795e[curl] Assume long encryption keys are base64 encoded📊 Changes
1 file changed (+28 additions, -9 deletions)
View changed files
📝
src/curl.cpp(+28 -9)📄 Description
Amazon SSE-C https://tinyurl.com/ychug4cg writes:
It seems likely that future keys would be as long, or longer, so
this change assumes that text longer than 32 characters are keys
that are base64 encoded.
Signed-off-by: Earl Chew earl_chew@yahoo.com
Relevant Issue (if applicable)
If there are Issues related to this PullRequest, please list it.
Details
Please describe the details of PullRequest.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.