https://bugzilla.novell.com/show_bug.cgi?id=463161
User tilman.vogel@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=463161#c8
Tilman Vogel changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P4 - Low |P2 - High
Status|RESOLVED |REOPENED
CC| |tilman.vogel@web.de
Resolution|INVALID |
--- Comment #8 from Tilman Vogel 2009-02-15 18:34:36 MST ---
This is not invalid. Steps to reproduce:
1. Append to /etc/pam.d/login (if not included)
auth optional pam_mount.so use_first_pass
session required pam_mount.so
2. Create an encrypted home for user "user"
3. Log in on /dev/tty1 as "user"
4. Log in on /dev/tty2 as "user" and run "mount".
You'll observe that /home/user is mounted twice. Once from /dev/loop0, once
from /dev/loop1.
This calls for any kind of trouble.
Reason and solution:
/sbin/mount.crypt should use the same DMDEVICE name for each mount. Actually,
in openSUSE 10.3, the following was in /sbin/mount.crypt (but had other flaws
causing the same trouble):
# if loop device, make device mapper name based on file pointed to
case "$DEVICE" in
/dev/loop*)
DMDEVICE=`losetup "$DEVICE" 2>/dev/null | sed 's/.*(\(.\+\)).*/\1/'`;
esac;
Putting this into /sbin/mount.crypt before
DMDEVICE="${DMDEVICE//\//_}";
will fix the issue.
There might be an upstream solution already, but I didn't check.
--
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.