On 12/18/17, Cindy-Sue Causey <butterflyby...@gmail.com> wrote: > On 12/18/17, to...@tuxteam.de <to...@tuxteam.de> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Mon, Dec 18, 2017 at 02:53:27PM +0100, Jeroen Mathon wrote: >> >> Don't forget to cc root kea, (s)he isn't on list. And oh, don't >> top post... pretty please :-) >> >>> I have never seen any stars in my Luks screen. >>> >>> As long as it decrypts the drive i see no real issue here. >> >> Perhaps root kea doesn't want others to see the passphrase's >> length? Perhaps it's just custom? Being able to configure >> that seems a legitimate wish, to me at least. > > > It crossed my mind, too, that root kea wanted to mask the ability to > see password length. I've relied a little on that password length hint > a time or two out on the Net when using my own passwords. > > These days I've noticed a few places will mask the length by showing > the wrong number of asterisks. I've seen it go either way where there > are more asterisks or less asterisks than the actual length of website > access passwords. If I encounter that feature again soon, I'll come > back and update with where it was seen.
Ok, I *literally* smacked myself in the head this time. The split second my first email here successfully posted, a thought occurred... Is it possible to pre-populate that field somehow in a way that doesn't change when any given user's moniker (username, account name, alias) is chosen? I'm imagining it to be in a similar way to how webmasters can define temporary, explanatory text in online form text fields. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA
