From: Christoph Hellwig <hch@lst.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Thomas Viehmann <tv@beamnet.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: permissions of /proc/tty/driver
Date: Sun, 16 Jan 2005 23:26:58 +0100 [thread overview]
Message-ID: <20050116222658.GA22364@lst.de> (raw)
In-Reply-To: <1105908524.12196.13.camel@localhost.localdomain>
On Sun, Jan 16, 2005 at 09:11:03PM +0000, Alan Cox wrote:
> On Sul, 2005-01-16 at 12:04, Christoph Hellwig wrote:
> > > (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.
>
> The file containts transmit and receive byte counts, which means you can
> both measure intercharacter delay and character count. Thats a big help
> to password guessers
I know. But that doesn't explain why we don't keep strict permissions
only on that file but on the directory.
next prev parent reply other threads:[~2005-01-16 22:31 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 ` permissions of /proc/tty/driver Christoph Hellwig
2005-01-16 13:13 ` 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 [this message]
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=20050116222658.GA22364@lst.de \
--to=hch@lst.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.