Encrypted home inaccessible after iso upgrade

Bug #1206640 reported by Michael Nelson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ecryptfs-utils (Ubuntu)
Expired
Undecided
Unassigned
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Steps to reproduce:
 1) Start with an existing ubuntu installation [1] with an encrypted home directory for 'username'
 2) Create a bootable USB of 13.10, reboot to installer and choose the "upgrade your existing ubuntu installation" (ie. keep the home directory)
 3) When prompted for a user name/passphrase, enter the same "username" and passphrase (I assumed it'd either realise it was the same or tell me to choose a different username)
4) After completion/reboot, login to the (only) 'username' account

Expected result:
 * Login works with encrypted home being unencrypted with the (same) passphrase

Actual result
 * Login flicks away from login screen, but then immediately returns without explanation, leaving the user unable to login.

After initial panic, it turns out it was pretty simple to rectify. Doing `ls -al` for /home/username (in a rescue console) showed that all the encrypted file data was owned by uid/gid 1001 (the old username I assume). The new 'username' user had uid/gid of 1000. To fix I did the following:
 1) Reboot and choose the "Ubuntu advanced options" grub menu item, then root shell.
 2) Ensure / is writable with `mount -o remount,rw /`
 3) `usermod --uid 1001 username`
 4) `groupmod --gid 1001 username`
Reboot and login as normal.

I'm assuming there's nothing that needs to change in ecryptfs-utils but I'll add it just in case so Dustin et al can verify.

[1] Note: as I'd previously upgraded to 13.10 via apt but experienced issues, I was really overriding the existing 13.10 ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Tue Jul 30 20:14:41 2013
EcryptfsInUse: Yes
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michael Nelson (michael.nelson) wrote :
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1206640

and any other logs that are relevant for this particular issue.

Changed in ecryptfs-utils (Ubuntu):
status: New → Incomplete
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ecryptfs-utils (Ubuntu) because there has been no activity for 60 days.]

Changed in ecryptfs-utils (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.