Re: On the road to the next release: testing the installer

[Tomas Volf <~@wolfsden.cz>]

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

On 2024-02-10 11:43:33 +0100, Vivien Kraus wrote:
> Le vendredi 09 février 2024 à 12:24 +0100, Tanguy LE CARROUR a écrit :
> > Grub asked me right away my passphrase and… it did not work! 😱
> > After several attempts, I figured out that the keyboard layout
> > was apparently set to `qwerty` even though I had selected `bépo
> > AFNOR`
> > during the configuration. When I eventually typed my passphrase
> > in `querty` Grub started and boot my system and… I had to type the
> > passphrase a second time, but, fortunately this time in `bépo`!
> > I checked the `config.scm` and the layout was properly set in the
> > bootloader declaration.
> This is unfortunate, but a known workaround is to boot and log in, then
> run cryptsetup luksAddKey <the device>, then enter your passphrase (to
> unlock the drive), then switch your keyboard layout to qwerty, then hit
> the exact same keys, and confirm by hitting the exact same keys. So
> now, you can unlock the drive with either your passphrase in a bépo
> layout or your passphrase in a qwerty layout.
>

It would probably make sense to have the second (qwerty) password in the first
key slot, to make the unlocking faster.

Or, just use the key file unlock and enter password just once (albeit it would
be the qwerty one).

Have a nice day,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]