[arch-general] systemd 220 crypt swap
I had to downgrade to systemd 219 because 220 fails to stop or enable luks crypt swap partition. There was an unlogged error on shutdown after upgrade and an infinite loop/wait on startup. I had to use a rescue linux to mount and disable crypttab and fstab entries before downgrading. /etc/crypttab: cswap /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256 /etc/fstab: /dev/mapper/cswap none swap defaults 0 0 Found nothing relevant about API breakage in v220 changelog.
On 05/25/2015 11:37 AM, Carsten Mattner wrote:
I had to downgrade to systemd 219 because 220 fails to stop or enable luks crypt swap partition.
...
/etc/crypttab: cswap /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256
... For comparison, I have no issues at all with 220 - my crypttab has this: swap UUID=<xxx> none luks,timeout=0 where xxx is the UUID. gene
On Mon, May 25, 2015 at 10:25 PM, Genes Lists
On 05/25/2015 11:37 AM, Carsten Mattner wrote:
I had to downgrade to systemd 219 because 220 fails to stop or enable luks crypt swap partition.
...
/etc/crypttab: cswap /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256
...
For comparison, I have no issues at all with 220 - my crypttab has this:
swap UUID=<xxx> none luks,timeout=0
where xxx is the UUID.
gene
That's not really the same thing, is it? Is the key random (one-time)? If your config is the right way and does the same thing, then the samples in the config file are either wrong or outdated. I suspect something broke in either crypttab handling or partition management.
On 05/26/2015 05:08 AM, Carsten Mattner wrote:
That's not really the same thing, is it? Is the key random (one-time)?
Nope it's not the same thing. That's what I meant by 'for comparison' :) ...
On Tue, May 26, 2015 at 2:41 PM, Genes Lists
On 05/26/2015 05:08 AM, Carsten Mattner wrote:
That's not really the same thing, is it? Is the key random (one-time)?
Nope it's not the same thing. That's what I meant by 'for comparison' :) ...
I didn't generate/install a new initramfs after upgrading to v220, so I don't think I'm affected by https://bugs.archlinux.org/task/45086. Therefore: https://bugs.archlinux.org/task/45105
participants (2)
-
Carsten Mattner
-
Genes Lists