One day I needed to open my veracypt container but had no internet nor veracrypt installed. I noticed that modern versions of cryptsetup can open veracrypt volumes with tcryptOpen --veracrypt <device> Is there any reason why cant luks be replaced with veracrypt in crypttab? https://www.freedesktop.org/software/systemd/man/crypttab.html and entry be created in fstab to use veracrypt encrypted partition as root partition. It seems that cryptsetup v1.6.6 is capable of mapping (mounting) tc volumes but v2 is also capable of mapping veracrypt volumes with --veracrypt flag
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am noob and still unable to test this out. Seems that this can only handle volumes using AES, Serpent, Twofish or any cascade of them but doesnt handle Camellia or Kuznyechik or any cascade that includes them. But the main question is still unanswered: what prevents veracrypt based linux distro encryption if any cryptsetup can limitedly open veracrypt volumes (just like it opens luks) and can work before mounting the "/" partition where linux then would store all data exept "/boot". So why cant cryptsetup replace veracrypt bootloader in linux cases? cryptsetup cant create or modify veracrypt partitions (headers) but can open them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One day I needed to open my veracypt container but had no internet nor veracrypt installed. I noticed that modern versions of cryptsetup can open veracrypt volumes with
tcryptOpen --veracrypt <device>Is there any reason why cant luks be replaced with veracrypt in crypttab? https://www.freedesktop.org/software/systemd/man/crypttab.html and entry be created in fstab to use veracrypt encrypted partition as root partition. It seems that cryptsetup v1.6.6 is capable of mapping (mounting) tc volumes but v2 is also capable of mapping veracrypt volumes with --veracrypt flagI am noob and still unable to test this out. Seems that this can only handle volumes using AES, Serpent, Twofish or any cascade of them but doesnt handle Camellia or Kuznyechik or any cascade that includes them. But the main question is still unanswered: what prevents veracrypt based linux distro encryption if any cryptsetup can limitedly open veracrypt volumes (just like it opens luks) and can work before mounting the "/" partition where linux then would store all data exept "/boot". So why cant cryptsetup replace veracrypt bootloader in linux cases? cryptsetup cant create or modify veracrypt partitions (headers) but can open them.