On 15/10/2020 17.54, Ralph wrote:
On Wed, 14 Oct 2020 14:30:59 +0200 "Carlos E. R." <> wrote:
On 14/10/2020 13.39, Ralph wrote:
Well, what you see is the expected behaviour, and I have seen it for years. plymouth captures and caches the passphrase for using it on other partitions. If plymouth is disabled, then nothing does the same job.
No, that is not expected behavior. Previously, plymouth.enable=0 did NOT stop the pw caching from working, it still worked (and still works) on my remaining 15.1 boot. Something else is involved here.
Correction. It was the expected behaviour for many years, till at some point in time systemd caught up and did the caching. I have a computer where it doesn't work, with 15.1, and I use the file trick. Plymouth is not even installed.
There is a trick, which is to add to all LUKS partitions another key, stored in a file, which resides in the first partition to be opened. On boot, that partition is opened, and the other partitions use that keyfile to be opened without prompting for the passphrase.
This 'trick' would seem to have the same problem as other 'unofficial' temporary fixes: when you next do a fresh install you have to remember all the temporary fixes you had installed in the previous system and re-install them in the new system, and this as I just found out (again) is not an easy thing even if you kept copious notes.
Well, I never reinstall, I upgrade :-D (yes, it is one of the things that is in my notes)
One simple example: I have a mlocate database in my /home. Official changes that were made to o/s stopped this from working. I installed a provided temporary fix / manual edit that allowed the updatedb/locate to again work on this local database. A permanent fix was supposedly submitted and accepted into the o/s. But, as I just discovered when first running my new install, that permanent fix doesn't work, which I didn't know before as I still had the temporary work-around installed on the old system. In this case I remembered the work-around, it was only 2 years ago :) so I just reinstalled it, and all is good, but I've still got other unrelated problems in the new system that I am scratching my head saying 'why doesn't this work like it used to'? So I would hesitate to use your 'trick' solution unless it is a life or death situation, which this is fortunately not :)
Heh :-D -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)