[Bug 853580] New: YaST does not create encrypted home folder when creating user
https://bugzilla.novell.com/show_bug.cgi?id=853580 https://bugzilla.novell.com/show_bug.cgi?id=853580#c0 Summary: YaST does not create encrypted home folder when creating user Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: fredvej@yahoo.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 On a fresh installed OpenSUSE 13.1 I want to create a new user with an encrypted home directory. I can't make it work, no matter what I do I just get two unused files in /home and an unencrypted normal home directory for the user. I boot the PC and login as root, start "Control Center" and choose "User and Group Management". In "Users" tab I click Add to create the new user. On the User Data tab I fill in user name and password and then click on the Details tab. Here I mark "Use Encrypted Home Directory" and the Directory Size in MB turns to 100. Now I click OK to exit the setup for the new user. In the main window I click OK again to apply the creating, The "Writing User and Group Configuration" checks the first four lines, but stops on "Write passwords". Error message box "stat: No such file or directory. Failed to open image". I click OK to close the error, and the configuration continues and then exits. In addition to the normal home directory /home/username, in /home appears two files: username.img sized 100 MiB and username.key 288 bytes. So the new user should be created OK, right ? Well, I can login as the new user, but the encryption is not activated, and the username.img is just, 100 MiB NULL bytes and never changes. No /dev/loop is in use, and df shows no sign of a mounted encrypted loop file. So I try again, reboot PC to get a clean slate and login as root and move the two files into hiding and then use YaST to delete the user, including deleting the home directory. Another reboot to make sure the user is gone, and then I bring back the two files to /home, and try to create the user again. This time the error message is "/home/username.img already exists. Use --force to overwrite it." I click OK, and the user is created, but still the encryption is not used. Reproducible: Always Steps to Reproduce: 1.Create new user, mark "Use Encrypted Home Directory" 2.Login as new user Actual Results: In addition to the normal home directory /home/username, in /home appears two files: username.img sized 100 MiB and username.key 288 bytes. I can login as the new user, but the encryption is not activated, and the username.img is just, 100 MiB NULL bytes and never changes. No /dev/loop is in use, and df shows no sign of a mounted encrypted loop file. Expected Results: Login as the user should mount the encrypted loop file and use that for the content of the user's home directory. OpenSUSE 13.1 64 bit, KDE desktop Intel Haswell HD4400 graphics -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=853580 https://bugzilla.novell.com/show_bug.cgi?id=853580#c1 Vladimir Moravec <vmoravec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |DUPLICATE --- Comment #1 from Vladimir Moravec <vmoravec@suse.com> 2013-12-05 09:28:13 UTC --- Hi, thanks for reporting this, this is a known bug and the issue is outside of yast, see this bnc#824087 . The workaround for that problem is calling `modprobe loop` before going to create a new user with encrypted home. *** This bug has been marked as a duplicate of bug 824087 *** http://bugzilla.novell.com/show_bug.cgi?id=824087 -- 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.
participants (1)
-
bugzilla_noreply@novell.com