https://bugzilla.novell.com/show_bug.cgi?id=734746 https://bugzilla.novell.com/show_bug.cgi?id=734746#c0 Summary: Encrypted home directory not unmounted Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lylavoie@iol.unh.edu QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 Encrypted home directory (created through yast, at time of user creation) is not unmounted when user logs out. I also don't believe it is gracefully unmounted during shutdown, which is leading to filesystem errors. Second symptom is, if the user logs out and logs back in, with no reboot in between, a second loop device is setup and re-mapped to the mapper device, and this new device is mounted a second time. For example, after a second log in, the following output from mount would appear: /dev/mapper/_dev_loop0 on /home/lylavoie type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) /dev/mapper/_dev_loop1 on /home/lylavoie type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) Reproducible: Always Steps to Reproduce: 1. Create user with encrypted home directory, done using yast 2. Login as user, causing encrypted home directory to be mounted (I only verified this behavior in GNOME and KDE, and not in a non-graphical shell. 3. Logout from the system 4. login as a root (by-passing what would be the mounting for the user) 5. Examine mounted filesystems, seeing home directory for user is still mounted through the loop device. 6. Re-login as user, and examine mounted filesystems. Result is user's home directory is mounted twice, on two different loop devices and mappings. Actual Results: User's encrypted home directory will appear to be mounted twice. Expected Results: On logout, GDM or other responsible component, MUST umount the user's encrypted home directory. This is necessary for both security reasons and to protect the integrity of the filesystem of the encrypted directory/image. I've marked this a critical, as the corruption of the home directory's filesystem on the encrypted image will cause data loss. This corruption seems to happen as a result of not unmounting the encrypted home directory during shutdown. It may be further complicated if the mount process is not actually recovering the journal of the filesystem as well. It does not appear possible to easily see the output of these processes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.