This is reproducible with a default "use full disk" and "encrypt my home
dir" installation. This produces that kind of crypttab which apparently
never initializes the cryptswap partition. blkid -p on that partition is
empty, there is no LUKS file system on it. I'm not sure about the role
of UUID for a cryptswap device that gets initialized from /dev/urandom,
but I figure there's supposed to be an outer LUKS wrapper around the
"inner" swap partition?
This is broken under upstart as well, it's just that booting silently
ignores the missing cryptswap partition and you have a system without
any swap.
** Summary changed:
- cryptswap (with ecryptfs) configures invalid crypttab
+ ecryptfs install does not initialize cryptswap partition
** Changed in: systemd (Ubuntu)
Status: Incomplete => Triaged
** Package changed: systemd (Ubuntu) => ubiquity (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429354
Title:
ecryptfs install does not initialize cryptswap partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1429354/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
