linux-kernel - Re: [PATCH] Use PC-BIOS NUMLOCK flag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.0.999.0810161958450.5051@be1.lrz>
Date:	Thu, 16 Oct 2008 20:00:31 +0200 (CEST)
From:	Bodo Eggert <7eggert@....de>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>
cc:	Bodo Eggert <7eggert@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Use PC-BIOS NUMLOCK flag

On Thu, 16 Oct 2008, Samuel Thibault wrote:
> Bodo Eggert, le Thu 16 Oct 2008 13:59:49 +0200, a écrit :

> > +	  If you have an alternative firmware like OpenFirmware or LinuxBios,
> > +	  this flag might not be set correctly, which results in a random state
> > +	  of the Numlock key.
> 
> That's an issue. That means that distributions will just not enable,
> and thus the flag is not really useful, since people who would
> compile their own kernel would very likely have already setup their
> initialization scripts into calling setleds +num (or just set LEDS=+num
> in /etc/console-tools/config on a debian machine).

I hope somebody will pop up and say "Hey, those will create an IBM PC data 
area, because they run DOS" ...
-- 
"Try to look unimportant; they may be low on ammo."
-Infantry Journal