public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Thomas Viehmann <tv@beamnet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: permissions of /proc/tty/driver
Date: Sun, 16 Jan 2005 13:04:36 +0100	[thread overview]
Message-ID: <20050116120436.GA13906@lst.de> (raw)
In-Reply-To: <41E80535.1060309@beamnet.de>

On Fri, Jan 14, 2005 at 06:45:25PM +0100, Thomas Viehmann wrote:
> Hi.
> 
> This may not be stritly on topic, but I couln't figure out a better 
> place to ask:
> 
> During the packaging of an application, I have the following problem:
> I would like to run a daemon as non-root. The daemon likes to 
> (continually) check /proc/tty/driver/usbserial to see whether or not 
> interesting USB devices  are connected. The permissions of this actual 
> file is (on a kernel compiled from Debian's kernel-source-2.6.10) 0444, 
> so this isn't a problem. However, the parent directory /proc/tty/driver 
> is 0500. I'm not sure whether this is related to Debian DSAs 358 or 423 
> (where /proc/tty/driver/serial is mentioned as leaking sensitive 
> information), to me the contents of usbserial look innocent enough.
> Do you have any hints on what might be a good solution?

The permissions on the directory look indeed too strict to me.  It might
be better to just use strict permissions on /proc/tty/driver/serial
indeed.

Counter-question:  What information is available in
/proc/tty/driver/usbserial but not in sysfs?

       reply	other threads:[~2005-01-16 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41E80535.1060309@beamnet.de>
2005-01-16 12:04 ` Christoph Hellwig [this message]
2005-01-16 13:13   ` permissions of /proc/tty/driver Thomas Viehmann
2005-01-16 19:13     ` Sergey Vlasov
2005-01-19 10:32     ` Christoph Hellwig
2005-01-16 21:11   ` Alan Cox
2005-01-16 22:26     ` Christoph Hellwig
2005-01-17  8:14       ` Arjan van de Ven
2005-01-17 12:23         ` Alan Cox

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=20050116120436.GA13906@lst.de \
    --to=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tv@beamnet.de \
    /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