Failover for LUKS without available text key
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
#402 Failover for LUKS without available text key
Hi,
There can be scenarios where one can have one root FS LUKS partition with a typable key, but others without, i.e.:
-
Encrypted swap partition with a throw-away random key, with a crypttab entry such as :
cryptswap1 UUID=<some-uuid> /dev/urandom swap,offset=1024,cipher=aes-xts-plain64,discard
Here the key will be generated and used, but not kept (swap contents will be lost at poweroff)</some-uuid> -
Secondary partition with binary keyfile hosted on the root fs, with a crypttab entry such as :
data UUID=<some_uuid> /crypto_keyfile.bin discard,luks
Here the binary key for the secondary container(s) is gotten from the root FS, once it has itself been successfully opened.</some_uuid>
In those examples, Clonezilla will ask for the root FS key, then will ask for the other LUKS partition key, but there is none that the user could type, so Clonezilla will fail opening the 2nd LUKS partition and bail out in error.
In such a case it would be nice that instead of bailing out in error, it could propose to save the LUKS partition as raw data without opening it - as it previously did before it became able to open LUKS partitions...
Per your request, Clonezilla live 3.0.3-20 has addressed this issue. Please give it a try:
https://clonezilla.org/downloads.php
Let us know the results. Thanks.
Steven