Tag Info

New answers tagged

0

It sounds like the key file that you are trying to use is at least 8 KiB, which exceeds cryptsetup's default maximum size. You can use the --new-keyfile-size <size_in_bytes> option to force cryptsetup to use the key, but I recommend using a random key with a smaller size, because a key that is larger than the master key of the LUKS volume offers no ...


0

Try this: You need to Boot into a Live DVD/USB environment and open up a terminal window: Press Applications --- Accessories--- Terminal Install required packages using the following commands: sudo apt-get update sudo apt-get install lvm2 cryptsetup Probe required module using the following command: sudo modprobe dm-crypt You find out which drive ...


1

You have LVM volumes inside the LUKS container. You should let the sytem know about them. Run sudo vgscan sudo vgchange -a y and then mount /dev/mapper/ubuntu--vg-root /mnt/whateveryoulike


0

In case anyone has the same problem, vgimportclone is your savior.


1

For LUKS, the only data that is critical for decryption is the LUKS header. The header can be backed up to a file with cryptsetup luksHeaderBackup and restored with cryptsetup luksHeaderRestore. See man cryptsetup: luksHeaderBackup <device> --header-backup-file <file> Stores a binary backup of the LUKS header and keyslot area. Note: ...


0

If you don't manage the loop device yourself, cryptsetup will automatically set up a loop device and close it when it is no longer needed. So there is no difference between the two; cryptsetup always works on the loop device. See man cryptsetup: NOTES ON LOOPBACK DEVICE USE Cryptsetup is usually used directly on a block device (disk partition or ...


0

See the "--allow-discards" option in the cryptsetup(8) man page and the "discard" option in the crypttab(5) man page.



Top 50 recent answers are included