** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1447282
Title:
Does not use encrypted swap whe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Vivid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
** No longer affects: systemd (Ubuntu Vivid)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1447282
Title:
Does not use encrypted s
So it is as I suspected:
* ecryptfs-setup-swap creates cryptswap1 at 512KiB offset of the former real
swap partition (vda3), and adds that to /etc/crypttab; as we need/want the
UUID, we keep the original swap header
* During boot, systemd-gpt-generator sees the apparent unencrypted swap
parti
Two ideas how to fix that:
* ecryptfs-setup-swap should change the partition type UUID to not be "swap"
any more so that we don't try and auto-activate it. This is my preferred
solution if it works.
* ecryptfs-setup-swap creates an override .swap unit which disables the
auto-mounting. But as
6 matches
Mail list logo