Created attachment 1313428 [details] SELinux denied sealert output Description of problem: Install a fresh Fedora 26 Workstation and create default admin user. After initial install and setup, login as root and run ecryptfs-migrate-home on said user. Confirm able to successfully login as that user after home dir encrypted via ecryptfs. Logout and notice as root that the user's home dir still mounted. Place SELinux in permissive mode and login as user again and then logout and notice how the home dir is automatically umounted. Even after playing around with entries noted in sealert -b. No suggested actions seem to allow ecryptfs to automatically umount user's home dir after they log out even after SELinux is no longer complaining about denied actions. Version-Release number of selected component (if applicable): ecryptfs-utils-111-2.fc25.x86_64 selinux-policy-3.13.1-260.3.fc26.noarch How reproducible: Always, disabling SELinux or putting it into permissive mode returns the behavior seen under Fedora 25 where with SELinux enabled encrypted home dir's would automatically umount after user logs out. Steps to Reproduce: 1. Install Fedora 26 and create a user. 2. Install ecryptfs-utils and migrate user's home dir. 3. Login and then logout and notice user's home dir still mounted when SELinux is in enforcing mode, but not true under permissive or disabled. Actual results: Encrypted home dir left mounted after user logs out. Expected results: Encrypted home dir automatically umounted after user logs out as it was in Fedora 25. Additional info: I am attaching some output relevant to the SELinux context's found via sealert.
This is what I see in my logs. The reproducer as described reproduces the issue. Aug 16 13:26:19 f26 audit[1762]: AVC avc: denied { getattr } for pid=1762 comm="umount.ecryptfs" name="/" dev="ecryptfs" ino=434176 scontext=system_u:system_r:mount_ecryptfs_t:s0-s0:c0.c1023 tcontext=system_u:object_r:ecryptfs_t:s0 tclass=filesystem #============= mount_ecryptfs_t ============== allow mount_ecryptfs_t ecryptfs_t:filesystem getattr;
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.