From: Krzysztof Halasa <khc@pm.waw.pl>
To: Rudolf Polzer <debian-ne@durchnull.de>
Cc: Horms <horms@verge.net.au>,
linux-kernel@vger.kernel.org, 334113@bugs.debian.org,
Alastair McKinstry <mckinstry@debian.org>,
security@kernel.org, team@security.debian.org,
secure-testing-team@lists.alioth.debian.org
Subject: Re: kernel allows loadkeys to be used by any user, allowing for local root compromise
Date: Wed, 19 Oct 2005 21:32:53 +0200 [thread overview]
Message-ID: <m3y84pjo9m.fsf@defiant.localdomain> (raw)
In-Reply-To: <20051019132326.GA31526%atfield-dt@durchnull.de> (Rudolf Polzer's message of "Wed, 19 Oct 2005 15:23:26 +0200")
Rudolf Polzer <debian-ne@durchnull.de> writes:
>> Ok. So they are exposed to known attacks with quite high probability.
>
> Which others? Are there other places that assume only trusted users can
> access
> the console?
Probably: BIOS booting, messing with computer cases (are the computers
in locked room and only kbds/monitors/mouses are accessible?), sniffing
keyboard cables (all other passwords if not root's), physical damage
to the computer hardware (some kind of DoS).
Still, may be adequate for student room.
>> I assume that one can notice that Ctrl-Alt-Backspace doesn't work,
>> and stop there.
>
> Not if a malicious X program does "chvt 1; chvt 7" when Ctrl-Alt-Backspace is
> pressed.
With correct timing, possibly. Depends on how the graphics driver starts
and switches from text mode. There might be noticeable differences.
> It would require a video driver that can actually reset the video mode.
> Framebuffer drivers usually can do that. For the standard VGA text mode, at
> least savetextmode/restoretextmode from svgalib don't work on the graphics
> cards I have.
I think Xserver could terminate gracefully. But it would require changes
to kernel SAK handling I think - not sure if it's worth it, given other
threats.
Another idea: if the machines are ACPI-enabled and have "soft-power"
buttons, one can make use of acpid.
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-10-19 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EQofT-0001WP-00@master.debian.org>
2005-10-18 4:41 ` Horms
2005-10-18 6:52 ` [Security] " Andrew Morton
2005-10-18 8:59 ` Horms
2005-10-18 14:42 ` Krzysztof Halasa
2005-10-18 17:16 ` Rudolf Polzer
2005-10-18 18:41 ` Krzysztof Halasa
2005-10-18 20:49 ` Rudolf Polzer
2005-10-19 11:18 ` Krzysztof Halasa
2005-10-19 13:23 ` Rudolf Polzer
2005-10-19 19:32 ` Krzysztof Halasa [this message]
2005-10-19 20:24 ` Rudolf Polzer
2005-10-19 22:57 ` Krzysztof Halasa
2005-10-19 23:12 ` Rudolf Polzer
2005-10-20 15:05 ` Krzysztof Halasa
2005-10-19 4:14 ` [Secure-testing-team] " Anthony DeRobertis
2005-10-19 11:00 ` Krzysztof Halasa
2005-10-20 2:42 ` Paul Jakma
2005-10-20 23:22 ` Bill Davidsen
2005-10-18 21:19 ` [Secure-testing-team] " Moritz Muehlenhoff
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=m3y84pjo9m.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=334113@bugs.debian.org \
--cc=debian-ne@durchnull.de \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mckinstry@debian.org \
--cc=secure-testing-team@lists.alioth.debian.org \
--cc=security@kernel.org \
--cc=team@security.debian.org \
/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®