Ubuntu
user-setup package

Jaunty Alpha 2 Installation: encrypted home directory broken

Bug #309541 reported by Dustin Kirkland 
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ecryptfs-utils (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Critical
Tim Gardner
Ubuntu jaunty-alpha-3
user-setup (Ubuntu)
Fix Released
Critical
Unassigned
Ubuntu jaunty-alpha-3

Bug Description

Binary package hint: user-setup

The Jaunty Alpha2 server and alternate installations offer a new option just after creating the initial user.

This option is supposed to setup the user's home directory for encryption.

Unfortunately, this is not working, due to missing kernel modules (ecb).

If you select this option, the user will be created, however the encrypted home directory setup will not complete. This will yield an unwritable (500) home directory, and your /etc/skel will be missing.

If you are suffering from this problem in post installation, as a temporary workaround, you can:
 $ sudo passwd # set a root password
 $ exit
 login: root
 # userdel -r $YOUR_USER
 # rm -rf /var/lib/ecryptfs/$YOUR_USER
 # adduser --encrypt-home $YOUR_USER
 # exit
 login: $YOUR_USER

This should be solved very shortly after Alpha2 in the daily iso's with an update to the crypto-modules package (and possibly some appropriate modprobing by user-setup).

:-Dustin

:-Dustin

Tags: iso-testing

Related branches

lp:ubuntu/lucid/user-setup
Dustin Kirkland  (kirkland)
Changed in user-setup:
importance: Undecided → Critical
status: New → Triaged
Changed in ecryptfs-utils:
status: New → Invalid
Changed in linux:
assignee: nobody → timg-tpi
importance: Undecided → Critical
milestone: none → jaunty-alpha-3
status: New → Triaged
Changed in user-setup:
milestone: none → jaunty-alpha-3
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Jaunty commit 'UBUNTU: Build in Crypto modules AES, CBC, ECB'

Changed in linux:
status: Triaged → Fix Committed
Revision history for this message
Colin Watson (cjwatson) wrote :

BTW, building in those modules was totally unnecessary - they could just have gone in the crypto-modules udeb, which user-setup is going to start attempting to install (just in case you decide to revert this).

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package user-setup - 1.23ubuntu4

---------------
user-setup (1.23ubuntu4) jaunty; urgency=low

  * Install crypto-modules if home directory encryption is requested
    (LP: #309541).
  * Re-enable home directory encryption option.

 -- Colin Watson <email address hidden> Tue, 06 Jan 2009 00:21:36 +0000

Changed in user-setup:
status: Triaged → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

Fixed in linux 2.6.28-4.5 (thanks!).

Changed in linux:
status: Fix Committed → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

Also see linux 2.6.28-4.9.

Revision history for this message
Mike (bild85) wrote :

still seeing similar behavior in Jaunty Alpha 4. After initial login was successful, subsequent logins fail. The desktop background displays but the desktop and task bars never appear. dmesg was full of the following error:

encrypt_decode_and_decrypt_filename: could not parse tag 70 packet from filename; copying through filename as-is

Revision history for this message
Mike (bild85) wrote :

my prob may be unrelated. Tried Dustin's solution and still get a blank desktop upon login, even when excluding the --encrypt-home option. Am not seeing the above error in dmesg now. Probably bailing on Alpha 4 for now.

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 309541] Re: Jaunty Alpha 2 Installation: encrypted home directory broken

Hmm, I was actually able to install just fine with the Alpha4 Jaunty
desktop livecd (amd64) with encrypting home.

Are you seeing a problem with this media?

:-Dustin

Revision history for this message
Mike (bild85) wrote :

I ran the media check and it succeeded. During the install the auto-partition didn't recognize my dual-boot setup, so I used the manual method and just formatted my previous EXT3 (/) to EXT3 again (tried EXT4 but that failed - don't remember the details, but we're already way OT). Maybe I'll try a fresh install again using encrypted home since it worked for you.

Ubuntu QA Website (ubuntuqa)
tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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