On Mon 03 Jan 2022 at 16:25:47 (+1100), David wrote: > On Mon, 3 Jan 2022 at 14:05, David Wright <deb...@lionunicorn.co.uk> wrote: > > On Thu 30 Dec 2021 at 19:48:05 (-0800), pe...@easthope.ca wrote: > > > > In weston, keyboard response can be hyper-typematic. > > > The kbdrate can be set at @reboot in root's > > crontab to make it possible to login at a text VC more > > easily, if it's messing up your typing passwords. > > Re early setting of typematic ... > > These days all my root filesystems are in LUKS containers. > > And one of my laptops was so hyper-typematic that there > was about a 50% chance of getting the 'cryptsetup open' > password accepted when prompted by the initrd. > > While this was great for security ($ADVERSARY has > difficulty to boot the machine even if they stole the > password!), it was a bit inconvenient. And also not > great for security (gives $THEM multiple opportunities > to surveil your password as you type it over and over again) ;p > > So I now run 'kbdrate' inside the initrd. This seems to have > solved the problem there and in all subsequent layers.
I presume you do this by placing something like /sbin/kbdrate -r 8 -d 500 -s ± a shebang, into a file like /etc/initramfs-tools/scripts/<something>/kbdrate.sh Which <something> is appropriate? Cheers, David.
