mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1176] cipher_suites=AESGCM silently fails #618
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#618
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 @Teej42 on GitHub (Oct 16, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1176
Version of s3fs being used (s3fs --version)
V1.85
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.2
Kernel information (uname -r)
4.15.0-65-generic
GNU/Linux Distribution, if applicable (cat /etc/os-release)
CentOS Linux 7 (Core)
s3fs command line used, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
Note: There appears to be no log in this docker image or LogDNA related to this issue. Return code for above command is
0.df -hdoes not show the mount.Details about issue
On CentOS docker image with yum install, s3fs silently fails when using
cipher_suitesoption that is apparently not supported. The specific version is:The same command on my Mac on the same network works and was installed using brew. Version is:
There are two concerns:
AESGCMcypher does not work, despite instructions on this page seemly claiming so:https://medium.com/@ozeri/file-like-access-to-ibm-cloud-object-storage-using-s3fs-f5094ed42594
cipher_suitessilently fails without any notification. It needs to loudly proclaim that this option is not compatible with whatever settings/packages that is being used.Please advise.
@gaul commented on GitHub (Feb 3, 2020):
Could you share how to reproduce this? I'm not sure how to get the cipher mismatch.
@gaul commented on GitHub (Jun 23, 2020):
Closing due to inactivity. Please reopen if symptoms persist.