public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Dabrunz <od@suse.de>
To: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: [Patch] TIOCCONS security
Date: Wed, 25 Aug 2004 17:11:06 +0200	[thread overview]
Message-ID: <20040825151106.GA21687@suse.de> (raw)

Hi,

the ioctl TIOCCONS allows any user to redirect console output to another
tty. This allows anyone to suppress messages to the console at will.

AFAIK nowadays not many programs write to /dev/console, except for start
scripts and the kernel (printk() above console log level).

Still, I believe that administrators and operators would not like any
user to be able to hijack messages that were written to the console.

The only user of TIOCCONS that I am aware of is bootlogd/blogd, which
runs as root. Please comment if there are other users.

Is there any reason why normal users should be able to use TIOCCONS?

Otherwise I would suggest to restrict access to root (CAP_SYS_ADMIN),
e.g. with this patch.

--- drivers/char/tty_io.c.orig	2004-08-25 12:51:17.000000000 +0200
+++ drivers/char/tty_io.c	2004-08-25 17:05:15.097068780 +0200
@@ -1566,10 +1566,10 @@
 
 static int tioccons(struct file *file)
 {
+	if (!capable(CAP_SYS_ADMIN))
+		return -EPERM;
 	if (file->f_op->write == redirected_tty_write) {
 		struct file *f;
-		if (!capable(CAP_SYS_ADMIN))
-			return -EPERM;
 		spin_lock(&redirect_lock);
 		f = redirect;
 		redirect = NULL;

-- 
Olaf Dabrunz (od/odabrunz), SUSE Linux AG, Nürnberg


             reply	other threads:[~2004-08-25 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 15:11 Olaf Dabrunz [this message]
2004-08-25 15:15 ` [Patch] TIOCCONS security Christoph Hellwig
2004-08-25 15:16   ` Christoph Hellwig
2004-08-25 16:18     ` Olaf Dabrunz
2004-08-25 21:03       ` Kees Cook
2004-08-26 21:22         ` Valdis.Kletnieks

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=20040825151106.GA21687@suse.de \
    --to=od@suse.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