Description of problem: On logout ~/Private does not get unmounted automatically, i.e. files are not re-encrypted. Version-Release number of selected component (if applicable): $ rpm -q ecryptfs-utils ecryptfs-utils-111-22.fc34.x86_64 How reproducible: easy, 100% Steps to Reproduce: 1. set up ~/Private ( ## preparation $ sudo dnf install -y ecryptfs-utils $ sudo usermod -aG ecryptfs YOURACCOUNT $ sudo reboot ## configuration $ ecryptfs-setup-private - type your login password and press enter - press enter to generate mount passphrase - ~/Private and ~/.Private and ~/.ecryptfs/ are created - ~/Private contains "Access-Your-Private-Data.desktop" and "README.txt" and is not writeable, if not mounted) 2. log out and in again 3. ~/Private gets mounted automatically and is writeable for the user (at the moment due to SELinux policy problem it does not work, see bug #1984739) 4. log out Actual results: "~/Private" is still mounted. Expected results: "~/Private" gets unmounted. Additional info: You can verify unmounting with root-login and command `ls /home/YOURACCOUNT/Private` either on TTY, f.i. Ctrl+Alt+F3, or with SSH login. For SSH login you might need to enable sshd and root login (netinstall ISO allows both during installation; workstation ISO requires the following commands): $ sudo passwd root $ sudo systemctl enable --now sshd.service $ echo "PermitRootLogin yes" | sudo tee "/etc/ssh/sshd_config.d/60-custom.conf" $ sudo systemctl restart sshd.service
upstream bug report: https://bugs.launchpad.net/ecryptfs/+bug/1963772
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.