View Issue Details

IDProjectCategoryView StatusLast Update
0008954Kali LinuxGeneral Bugpublic2024-10-13 13:03
Reporterfisherman2001 Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0008954: Luks-Decryption of multiple partitions at boot time
Description

Hi,

I am using three luks encrypted disks for an bare-metal Kali installation.

nvme1n1p2_crypt UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx none luks,discard
nvme1n1p3_crypt UUID=yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy none luks,discard
nvme1n1p4_crypt UUID=zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz none luks,discard

<file system> <mount point> <type> <options> <dump> <pass>

/dev/mapper/nvme1n1p2_crypt / btrfs defaults,subvol=@ 0 0
... and all the other subvolumes ...
/dev/mapper/nvme1n1p3_crypt /data btrfs defaults 0 0
/dev/mapper/nvme1n1p4_crypt none swap sw 0 0

When I boot the system, Kali asks for an password for nvme1n1p2_crypt and for nvme1n1p4_crypt.
It seems to decrypt nvme1n1p2 and nvme1n1p3 with one password entry.
For nvme1n1p4 I must enter the password a second time.
All luks passwords are equal.
All disks can successfully be decrypted with that password (however, need to enter it twice).

There is just one thing I did during the installation.
In the partitioning dialog, I created the luks partitions for / and /data first.
The system wrote random data on the partitions, created the two luks containers and returned to the partitioning dialog.
In a second step, I created a luks partition for the SWAP (initially forgot it).
The system wrote random data on the partition, created the luks container and returned to the partitioning dialog.
I continued with the rest of the installation.

It somehow looks like if only the luks containers that were created together can be opened with a single password entry.
The swap partition, which was created separately, requires me to enter the password again.

Any idea, how I can get all three partitions being decrypted with just entering the password once?

Btw. to me it looks like decrypt_derived, decrypt_keyctl, etc. scripts are no longer being used by Kali and there is being another mechanism in place to decrypt multiple disks.
Is this correct?

Best regards
The fisherman

Activities

kali-bugreport

kali-bugreport

2024-10-12 09:39

reporter   ~0019900

Last edited: 2024-10-12 10:31

Is this really a bug report or rather a support question?

Do not request support or ask questions within the bug tracker. Kali Linux offers several options for support including Kali Docs, Kali forums, and our IRC chat room (#kali-linux on OFTC).

https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

And if really a bug probably should be forwarded to the developers of the software rather to the Kali bug tracker.

fisherman2001

fisherman2001

2024-10-13 13:03

reporter   ~0019901

Well, for me it looked like a bug in the installer.

I tried to solve it without reinstalling Kali as I hope to understand what went wrong during the installation.
However, I didn't found a root cause. Everything in the configuration looks to be right to me.

Not sure if it should be addressed within Kali or if it needs to be resolved by Debian?
However, I agree that it is a bug of a minor severity.

Issue History

Date Modified Username Field Change
2024-10-11 20:43 fisherman2001 New Issue
2024-10-12 09:39 kali-bugreport Note Added: 0019900
2024-10-12 10:31 kali-bugreport Note Edited: 0019900
2024-10-13 13:03 fisherman2001 Note Added: 0019901