> swapon -a by default
I'm not worried about default behaviour, just wondering what can go
wrong long term.
How about putting a keyless LUKS header on it. You can't do anything
with it (as the manpage states, "Removing the last passphrase makes the
LUKS container permanently inaccessible."). But it provides a UUID and
it makes the device look like it's supposed to be encrypted, which it
is.
echo swap | cryptsetup --batch-mode --iter-time=1 --uuid="$uuid" luksFormat
"$dev"
echo swap | cryptsetup --batch-mode luksKillSlot "$dev" 0
And then forget & ignore this header (only the first 4K need to be left
intact) and use plain cryptsetup with offset as it were.
I'm not sure what various mount helpers would make of such a "LUKS"
partition though. Ideally with the crypt mapping in place they should
recognize it as already open.
But maybe I'm just overthinking things. Sorry for butting in. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953875
Title:
Encrypted swap no longer mounted at bootup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
