Maybe also Ubiquity needs to be patched, I am not sure since I did not
have time to test it yet.

I did the following test to isolate the problems.


1) Fresh ubuntu 17.04 installation with no encrypted home (and no encrypted 
swap). /etc/crypttab is empty, and in /etc/fstab I have the following line:

/swapfile none            swap    sw              0       0


2) After successfully running ecryptfs-migrate-home, I run ecryptfs-setup-swap 
(the "original" version, not the one with the above patch) and I get:

INFO: Setting up swap: [/swapfile]
device node not found
WARNING: Commented out your unencrypted swap from /etc/fstab
swapon: cannot open /dev/mapper/cryptswap1:  No such file or directory

Now in /etc/fstab I have:

#/swapfile none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0

and in /etc/crypttab I have:
cryptswap1 UUID=98a3bb25-2c4d-4897-974c-d5dfcc16be8f /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64

If I run free, I see that I have no swap:
              total        used        free      shared  buff/cache   available
Mem:        8084440     1421116     4575096      273228     2088228     6086972
Swap:             0           0           0


3) I reboot, and the system hangs a lot during boot. I see "a start job is 
running for dev-mapper-cryptswap1.device". After a couple of minutes, the boot 
process ends and I can login. If I run "systemctl status swapfile.swap" and 
"free" I see that (unencryted) swapfile has been activated anyway.
THIS IS DIFFERENT FROM WHAT I GOT WHEN DOING A FRESH UBUNTU 17.04 INSTALL WITH 
THE "ENCRYPT HOME FOLDER" OPTION SELECTED.
In that case, I got the system hanging during boot, too, but when I finally 
managed to login I got no swap at all ("systemctl status swapfile.swap" 
returned "failed to activate swap /swapfile").
Looking at ubiquity scripts, I see that if encrypted home option is selected, 
it runs also ecryptfs-setup-swap (so ubiquity is actually affected by the bug 
described above); but the fact that system fails also to activate unencrypted 
swap seems to suggest that Ubiquity may need to be patched too.


4) 

** Description changed:

  Description:  Ubuntu Zesty Zapus (development branch)
  Release:      17.04
  ecryptfs-utils:
    Installato: 111-0ubuntu4
    Candidato:  111-0ubuntu4
    Tabella versione:
   *** 111-0ubuntu4 500
          500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
          100 /var/lib/dpkg/status
  
  Ubuntu 17.04 uses swapfiles by default.
  
  If you select the "encrypt home folder" option when creating the main
  user during Ubuntu 17.04 beta1 installation (which makes Ubiquity run
  also the ecryptfs-setup-swap command), after installation the system
  hangs a lot during boot, because it fails to activate swap (output of
  "systemctl status swapfile.swap" says "failed to activate swap
  /swapfile").
  
  If you install Ubuntu 17.04 beta1 without selecting "encrypt home
  folder", and only after installation you run the ecryptfs-migrate-home
  utility, everything works. But as soon as you try to manually setup
  encrypyted swap (by running ecryptfs-setup-swap), you get the same
  problem as above.
  
+ In particular, you get the following error when running ecryptfs-setup-
+ swap:
+ 
+ INFO: Setting up swap: [/swapfile]
+ device node not found
+ WARNING: Commented out your unencrypted swap from /etc/fstab
+ swapon: cannot open /dev/mapper/cryptswap1: No such file or directory
+ 
  This is due to an ecryptfs-utils bug.
  In particular, ecryptfs-setup-swap puts in /etc/crypttab a line like this:
  
  cryptswap1 UID=XXXXXXXX /dev/urandom swap,offset=1024,cipher=aes-xts-
  plain64
  
  (like there were a swap partition with UID=XXXXXXXX) while with a
  swapfile it should put the following line:
  
  cryptswap1 /swapfile /dev/urandom swap,offset=1024,cipher=aes-xts-
  plain64
  
  If you manually change that line and reboot, you get rid of the problem - 
before rebooting, check also that your /etc/fstab file ends with:
  #/swapfile none            swap    sw              0       0
  /dev/mapper/cryptswap1 none swap sw 0 0
  
- This bug indirectly affects also Ubiquity, since choosing the "encrypt
- home folder" makes system hang a lot at boot (and when it finally starts
- it has no swap).
+ This bug indirectly affects also Ubiquity, because when you choose the
+ "encrypt home folder" option during installation, ubiquity runs also
+ ecryptfs-setup-swap; since Ubuntu 17.04 uses swapfiles by default, and
+ ecryptfs-setup-swap does not work with swapfiles, after installation you
+ get the system hanging a lot at boot (and when it finally starts it has
+ no swap).
  
  I tried both with Ubuntu Budgie and with Ubuntu Gnome, the problem is
  the same.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ecryptfs-utils 111-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar  6 12:47:39 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ecryptfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670336

Title:
  Ubiquity problem with encrypted home option: system hangs because of
  ecryptfs-setup-swap not working with swapfiles

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1670336/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to