public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 13:18:32 +0200	[thread overview]
Message-ID: <m3oe5l21rr.fsf@defiant.localdomain> (raw)
In-Reply-To: <20051018204919.GA21286%atfield-dt@durchnull.de> (Rudolf Polzer's message of "Tue, 18 Oct 2005 22:49:19 +0200")

Rudolf Polzer <debian-ne@durchnull.de> writes:

> However, pool computers like in this case are neither servers nor terminals.
> If they were terminals, we would need about 30 servers to handle the load of
> 100 active students. So they are workstation installations that do most of
> the
> work locally.

Ok. So they are exposed to known attacks with quite high probability.
This might be acceptable (as they are student machines) but not secure.

>> Hope they don't change the keys in the process.
>
> They HAVE to do that,

Well, I meant physical keys to match them to loaded keymaps :-)

> Many people here need that, but it's ok for them if it works only in X11
> (most
> of these users don't even know that text consoles exist).

I see. X11 is another story, though.

> However, Xorg and XFree86 have about the same problem: you can remap
> Ctrl-Alt-Backspace. So it would be good if the SAK also worked there which
> would require it to set a "sane" video mode.

I assume that one can notice that Ctrl-Alt-Backspace doesn't work,
and stop there. I think SAK/X11 video mode issue is possible to fix,
though.
-- 
Krzysztof Halasa

  reply	other threads:[~2005-10-19 11:18 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 ` kernel allows loadkeys to be used by any user, allowing for local root compromise 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 [this message]
2005-10-19 13:23             ` Rudolf Polzer
2005-10-19 19:32               ` Krzysztof Halasa
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=m3oe5l21rr.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