mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #1411] SignatureDoesNotMatch host s3.us-west-000.backblazeb2.com #747
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#747
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?
Originally created by @socomsystems on GitHub (Sep 20, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1411
Been investigating this for 24 hours, no resolution yet. Have compiled on versions 1.87 and 1.85 using both openssl and gnutls, same issue resides all 4 variants.
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD
Version of s3fs being used (s3fs --version)
example: 1.00
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
example: 2.9.4
Kernel information (uname -r)
command result: uname -r
GNU/Linux Distribution, if applicable (cat /etc/os-release)
command result: cat /etc/os-release
s3fs command line used, if applicable
/etc/fstab entry, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages### Details about issue
@gaul commented on GitHub (Sep 20, 2020):
Can you test your credentials using the AWS CLI? First you need to add your B2 S3 credentials (these are different than your B2 credentials) to
$HOME/.aws/credentials:Next list your buckets:
I successfully mounted the bucket afterwards with s3fs.
@AlexTalker commented on GitHub (Sep 20, 2020):
@gaul I am too have struggle with connecting to B2 via
s3fs-fuse, but nowI filled in the command though(you missed
[backblaze]in config file example thou)and it works and then I filled in credentials in the mount example here and it works too.
I don't exactly get what I did wrong past time,
so this all gets interesting.
I think on some point I have seen the SignatureDoesNotMatch error too but I quickly went trying out other solutions.
I used EPEL package by the way.
@AlexTalker commented on GitHub (Sep 20, 2020):
This all is so confusing, especially when following the official guide ( https://help.backblaze.com/hc/en-us/articles/360047773653-Using-S3FS-with-B2 ) and it DIDN'T work probably because they skipped
-o use_path_request_style@socomsystems commented on GitHub (Sep 20, 2020):
@gaul I gave aws cli a stabb and it worked with no issue.
I then tried several different permutation orders of command line s3fs as installed v1.85 - all failed
I then went back to v1.87, recompiled but this time with both --with-gnutls and --with-nettle ...and snap, its looks like we're getting somewhere. Passed the cipher match, no multiuse support (bb may not support mus if I recall). Really odd though, something to do with libcurl and/or openssl is a misfire.
I'll keep at it. Anyone else able to reproduce what I'm seeing?
@socomsystems commented on GitHub (Sep 20, 2020):
Ok, openssl issue confirmed. I reconfigured as such only: ./configure --prefix=/usr --with-gnutls ...no other flags on 1.87 and was able to get as far as the last posts log. Failed to mention one package may have been missing as I did execute the following apt commands. If so, I didn't see it or was distracted.
@gaul commented on GitHub (Sep 21, 2020):
@socomsystems Great debugging! S3 servers emit
SignatureDoesNotMatchwhen either the headers or signature of the headers do not match. I wonder if OpenSSL is adding or overwriting a header? FWIW I successfully ran s3fs using OpenSSL 1.1.1g on Fedora 32.@socomsystems commented on GitHub (Sep 21, 2020):
Final Backblaze s3fs v1.87 in optimized for my environment fstab form factor
A possible perp to include in the lineup looks to be OpenSSL 1.1.1f 31 Mar 2020, libcurl and/or keys crossover. Not looking any further problem solved, closing thread. Thanks for chiming in guys.
@arichiardi commented on GitHub (May 4, 2021):
@socomsystems thanks for debugging this!
Was the problem with
OpenSSL 1.1.1f? I having the same problem within Clonezilla Live.@Telofy commented on GitHub (Jul 23, 2021):
FYI: I’ve had similar issues (though my error was
InvalidAccessKeyId) and tried to compile s3fs with OpenSSL, Nettle, and GNUTLS to no avail. The solution was to create a new key instead of the “Master Application Key” and use the new one.