public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars <lhofhansl@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10 breaks xconsole
Date: Sat, 25 Dec 2004 15:07:13 -0800	[thread overview]
Message-ID: <41CDF2A1.1040606@yahoo.com> (raw)
In-Reply-To: <41CDE70E.8090109@yahoo.com>

Lars wrote:
> Running kernel 2.6.10, xconsole always displays: Couldn't open console.
> xconsole works fine in the identical setup with 2.6.9 and 2.4.28.
> 
> The permissions are set correctly:
> crw-rw-r--  1 lars tty 5, 1 2004-12-25 13:17 /dev/console
> 
> xconsole won't work when run as either lars, a tty member, and even 
> root. In all cases the message above is shown.
> 
> If I change permission to:
> crw-rw-r--  1 root tty 5, 1 2004-12-25 13:17 /dev/console
> 
> xconsole can at least be run as root.
> 
> I guess this is related to this patch:
> <od@suse.de>
>     [PATCH] TIOCCONS security
> 
> Forcing xconsole to be run as root is not a good idea, IMHO.
> 
> -- Lars
> 
> ps. Please CC me directly as I'm not subscribed to the list.
> 

Fixed it by reversion this portion of the 2.6.10 patch to 
drivers/char/tty_io.c

@@ -1981,10 +2012,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;


-- Lars

      reply	other threads:[~2004-12-25 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25 22:17 2.6.10 breaks xconsole Lars
2004-12-25 23:07 ` Lars [this message]

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=41CDF2A1.1040606@yahoo.com \
    --to=lhofhansl@yahoo.com \
    --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