Using `cryptsetup status` I have checked on the cryptoswap device. Indeed, the type is different, though seemingly encrypted in both cases as a cipher is listed. I didn't attempt to verify that the swap is actually encrypted, I'm trusting the cipher/keysize values on that front.
At install time the type is LUKS2, and at first boot the type becomes PLAIN, matching the symlink shown under /dev/disk/by-id. Both Ubiquity and Curtin have this behavior now, but that makes sense as I copied the logic from the Ubiquity zsys-setup script into curtin. Marking this MP as WIP while I investigate to see if the type can be made to not change on first boot. -- https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/460156 Your team curtin developers is requested to review the proposed merge of ~dbungert/curtin:cryptoswap-dm-name into curtin:master. -- Mailing list: https://launchpad.net/~curtin-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~curtin-dev More help : https://help.launchpad.net/ListHelp
