[pkg-cryptsetup-devel] Issue with encrypted partition has been found while testing Debian Trixie.

[bugs at kojori.tel]

Hello cryptsetup developer team. 
I am reaching out to you because of the issue I have encounter while testing upcoming release of Debian Trixie. 

This issue affects systems where secondary physical storage block device present with a luks encrypted partition.

There is no issue with manually unlocking and mounting such partition on a local host. 

However, when a technique to auto-unlock and mount such partition, during the boot sequence is used, host hang's on boot.

Technique to auto-unlock and mount partition involves a setup with cryptsetup + generation and provisioning a key file + /etc/crypttab + /etc/fstab instructons. 

This technique has been used successfully on Debian 10, Debian 11, Debian 12.

However, there seems to be an issue, of some sort, with systemd while booting, where partition is not getting unlocked and mounted causing the host to hang on boot. 

I have created a ticket with details. please see: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100831

...however, the raised concern was dismissed.

I do not know how to proceed and who might be a best point of contact to relay my findings regarding this issue. 

If you could please advise what is the best way to approach this issue, I would really appreciate it. 

Thank you for your time and developing efforts. 

Damien