[patch] fix remote unlock of encrypted root with plymouth installed
Bug #1431039 reported by
Maddes
This bug report is a duplicate of:
Bug #595648: Remote unlocking not possible if plymouth is active (Bug or Feature?).
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cryptsetup |
New
|
Undecided
|
Unassigned | ||
Bug Description
The cryptroot script always uses plymouth if present (plymouth is installed by default on Ubuntu).
Unfortunately this prevents to unlock an encrypted root from console (e.g. via SSH).
Changes in /usr/share/
- new parameter "noplymouth": possible to use during boot time to avoid usage of plymouth even if present
- kill all processes which ask for password after encrypted root is available
New file /usr/share/
- creates /bin/unlock script in initramfs to define correct PATH and call cryptroot script with correct parameter
- creates /etc/motd file in initramfs to inform user about unlock script
Kind regards
Maddes
To post a comment you must log in.
