Description of problem: $ encfs /path/to/secure/directory/ /mnt/encfs/ Entered my password Version-Release number of selected component: fuse-encfs-1.9.5-13.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-9d4d9d5d-cb56-4184-9c01-1f72a5aa74d7.scope cmdline: encfs /store/Secure/ /mnt/encfs/ crash_function: EVP_CIPHER_CTX_set_key_length executable: /usr/bin/encfs journald_cursor: s=8a012c1e8503458ba0d514ac6ba938e9;i=2265d;b=b9b77530e0e54f7ca3dae10f388e8c3f;m=3a2b437b;t=5e1459feccde6;x=74681016aa4c5372 kernel: 5.17.13-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1889210 [details] File: backtrace
Created attachment 1889211 [details] File: core_backtrace
Created attachment 1889212 [details] File: cpuinfo
Created attachment 1889213 [details] File: dso_list
Created attachment 1889214 [details] File: environ
Created attachment 1889215 [details] File: exploitable
Created attachment 1889216 [details] File: limits
Created attachment 1889217 [details] File: maps
Created attachment 1889218 [details] File: mountinfo
Created attachment 1889219 [details] File: open_fds
Created attachment 1889220 [details] File: proc_pid_status
*** Bug 2097470 has been marked as a duplicate of this bug. ***
For me it happens on one directory and not another, seemingly related to old formats(?) Not working: * has .encfs5, which is binary junk * made by EncFS 1.3.2 (very old, I've had this dir for maybe 15 or so years) Working: * has .encfs6, which is xml * made by EncFS 1.7.4 gdb trace, looks same as the autogen stuff above to me: ``` Program received signal SIGSEGV, Segmentation fault. 0x00007ffff771a506 in EVP_CIPHER_CTX_set_key_length (c=0x5555555c3e80, keylen=20) at crypto/evp/evp_enc.c:985 Downloading 0.05 MB source file /usr/src/debug/openssl-3.0.5-1.fc36.x86_64/crypto/evp/evp_enc.c 985 if (c->cipher->prov != NULL) { (gdb) ``` I plan to try some old fedora system to copy the files into a new encfs. I'm not sure when this broken: possibly during my upgrade to Fedora 36 (I know it worked on Fedora 35 but I cannot be sure I have accessed this directory previously on Fedora 36 or not)
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.