Re: [solved] passphrase feedback when unlocking disk at boot
On Thu 23 Jan 2020 at 21:23:07 (+0100), Jonas Smedegaard wrote:
> Quoting David Wright (2020-01-23 20:51:13)
> > On Thu 23 Jan 2020 at 10:32:44 (-0800), Mike Kupfer wrote:
> > > Andrei POPESCU wrote:
> > > > On Jo, 23 ian 20, 07:49:01, Mike Kupfer wrote:
> > > > > With the first system, when I enter the passphrase at the
> > > > > "please unlock disk" prompt, there is no visual feedback. With
> > > > > the second system, I get a "*" for each character that I type.
> > > > >
> > > > > Is there some configuration option I can change on the first
> > > > > system so that it behaves like the second one?
> > > >
> > > > The package plymouth might be the difference.
> > >
> > > Yes, that was it. I installed plymouth on the first system and
> > > rebooted, and now it prints a "*" for each character in the
> > > passphrase.
> >
> > It would be interesting to know why installing plymouth made any
> > difference. My system prints asterisks even though plymouth is not
> > installed.
> >
> > Were there any other packages installed along with plymouth?
>
> Seems it is part of systemd to switch behaviour when plymouth is
> available:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1432265/comments/9
I don't understand much of that page.
But in any case, the user made their system print asterisks by
installing plymouth. So why does my system print them without
having plymouth installed? Is this just a DE problem rather
than a systemd one? (I don't have a DE.)
For me, the more interesting question would be how to ask for the
password when using udisksctl unlock in the same way as
happens during booting when crypttab is being acted upon. The
latter (crypttab) prints asterisks whereas the former (udisksctl) doesn't.
Cheers,
David.
Reply to: