From: "Olaf van der Spek" <olafvdspek@gmail.com>
To: mathias.schnarrenberger@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: security: delete BIOS password in keyboard buffer during kernel bootup
Date: Sat, 8 Nov 2008 17:39:17 +0100 [thread overview]
Message-ID: <b2cc26e40811080839i387e5e94o519a5d1ff0086379@mail.gmail.com> (raw)
In-Reply-To: <200811081100.03966.mathias.schnarrenberger@gmx.de>
On Sat, Nov 8, 2008 at 11:00 AM, Mathias Schnarrenberger
<mathias.schnarrenberger@gmx.de> wrote:
> Hi,
>
> I'm using a BIOS password in my notebook (nc6120 from HP). Recently I noticed that the HP BIOS doesn't clean the keyboard buffer after the password was correctly entered. I know that this is rather a BIOS thing but I assume that other BIOSes also don't clean the BIOS keyboard ring buffer (at adress from 0x0000041E up to 0x0000043D). Since after the kernel boot up the BIOS Keyboard ISR is deactivated no one cares about the data in the keyboard buffer. So, the BIOS password is kept in the buffer.
>
> So, I think it would be good if the kernel clears the keyboard buffer during boot up (at least in x86-based systems) to protect the users password. I don't know anything about EFI-based systems and other architectures.
> Because I'm not sure where to implement the code to delete the keyboard buffer in the kernel, I can't make a proper patch. Possibly one of you can do this ;)
What if my BIOS stores some critical info at that memory address?
I don't think the kernel is the right place to work around this issue.
next prev parent reply other threads:[~2008-11-08 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 10:00 Mathias Schnarrenberger
2008-11-08 14:27 ` Alan Cox
2008-11-08 14:36 ` Mathias Schnarrenberger
2008-11-08 16:39 ` Olaf van der Spek [this message]
2008-11-09 8:41 ` Mathias Schnarrenberger
2008-11-09 11:08 ` Alan Cox
2008-11-11 16:18 ` Pavel Machek
2008-11-11 16:54 ` Alan Cox
2008-11-12 8:51 ` Gerhard Mack
2008-11-09 15:36 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2cc26e40811080839i387e5e94o519a5d1ff0086379@mail.gmail.com \
--to=olafvdspek@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.schnarrenberger@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®