This really needs to be solved. Unlocking secure systems that use some external key device that requires a specific helper script to access is a significant use case.
According to the Debian bug report discussion it seems that upstream systemd aren't prepared to finish their replacement implementation of cryptsetup init scripts without some kind of major new generic functionality.
Ccan we workaround that by disabling systemd-cryptsetup and use the existing cryptsetup functionality?
This really needs to be solved. Unlocking secure systems that use some external key device that requires a specific helper script to access is a significant use case.
According to the Debian bug report discussion it seems that upstream systemd aren't prepared to finish their replacement implementation of cryptsetup init scripts without some kind of major new generic functionality.
Ccan we workaround that by disabling systemd-cryptsetup and use the existing cryptsetup functionality?