In addition encrypting on boot with a USB is not a reasonable workflow
in many cases for multiple reasons. Please specify how to go about
fixing these bugs namely:
1. Are these bugs stemming from unexpected behavior of Plymouth from the
standpoint of the API used by these programs. Eg, please spec
Do you understand that these specified bugs with Plymouth's behavior
and/or these critical crypto packages make it impossible to encrypt on
boot with a passphrase?
This is a fundamental feature and critical to running encrypted
services. Encryption of the home directory is functionally useless for
This bug remains. I was only able to resolve it functionally by
specifying a one letter p/w. With multiple character passwords, it
becomes impossible to submit the correct p/w. (both with regards to
libpam which is what I care about)
You want me to specify how to create a standard luks file contai