From: Stefan Gast <mrsteven@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Shouldn't the ioctl KDSKBMODE only be usable by root?
Date: Fri, 28 Apr 2006 13:41:27 +0200 [thread overview]
Message-ID: <e2sv1d$26ed$1@ulysses.news.tiscali.de> (raw)
Hi,
I'm a bit confused about the fact that everyone who has access to a virtual
console can stop the keyboard from working by using the KDSKBMODE ioctl:
ioctl(fd_to_console_or_tty, KDSKBMODE, K_RAW);
This is a problem because console switching via alt+fx is no longer possible
when the keyboard is in raw mode.
Why is everyone permitted to change the keyboard mode? I guess it is because
of the unicode support, but couldn't a modified unicode_start script be
called by root while running some init script?
The loadkeys (KDSKBENT) and setkeycodes (KDSETKEYCODE) programs fail because
of permisson problems when they are called by a non-privileged user. I
think that's correct, but an unprivileged user should not be able to make
the system unusable by using KDSKBMODE.
Stefan
reply other threads:[~2006-04-28 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='e2sv1d$26ed$1@ulysses.news.tiscali.de' \
--to=mrsteven@gmx.de \
--cc=linux-kernel@vger.kernel.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®