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: <20081016191106.GB4988@const.famille.thibault.fr>
Date:	Thu, 16 Oct 2008 21:11:06 +0200
From:	Samuel Thibault <samuel.thibault@...-lyon.org>
To:	Bodo Eggert <7eggert@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Use PC-BIOS NUMLOCK flag

Bodo Eggert, le Thu 16 Oct 2008 20:00:31 +0200, a écrit :
> 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" ...

Mmm, or rather "hey, here are the patches to fix those BIOSes" :)

Samuel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/