From: Catalin Patulea <cat@vv.carleton.ca>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Mason <mason@suse.de>
Subject: Re: [RFC][PATCH 0/3] Access Control Lists for tmpfs and /dev/pts
Date: Thu, 4 Aug 2005 15:39:51 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0508041531460.11315@vv.carleton.ca> (raw)
In-Reply-To: <1107365842.5712.16.camel@winden.suse.de>
On Wed, 2 Feb 2005, Andreas Gruenbacher wrote:
> On Wed, 2005-02-02 at 17:55, Christoph Hellwig wrote:
>> On Wed, Feb 02, 2005 at 05:13:40PM +0100, Andreas Gruenbacher wrote:
>>> Here is a set of three patches which implement some general
>>> infrastructure and on top of that, acls for tmpfs and /dev/pts files.
>>
>> Why would you want ACLs on /dev/pts?
>
> That's actually a good question. The patch allows to give several people
> access to the same terminal, which sometimes comes in handy with tools
> like screen (at least in its current version), and that's what the patch
> originally was meant for. I've just talked this over this with one of
> the maintainers though, and there are probably better ways than handling
> this at the file permission level, like passing open file descriptors
> between processes. So unless somebody comes up with a convincing
> application, that patch probably should stay out.
Aside from the above reason, I believe the mechanism behind the write
command should also be considered. The notifications generated by write
can currently be enabled and disabled only through an "all-on" or
"all-off" mechanism - it doesn't leave room for user- or group-specific
permissions because it's based on the mode of the TTY special file.
ACL support in devpts would allow much more fine-grained control of who
is allowed and who is denied access to writing messages on your terminal.
This would come in very handy and I personally believe it should be
possible to have such control.
Sorry for the random post and thanks for considering this reason,
Catalin Patulea
>
> Cheers,
> --
> Andreas Gruenbacher <agruen@suse.de>
> SUSE Labs, SUSE LINUX GMBH
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
-----------------------------------------
Catalin Patulea VV Volunteer 2002,3
http://vv.carleton.ca/~cat/ VV HI 2004,5
cat@vv.carleton.ca
prev parent reply other threads:[~2005-08-04 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 16:13 Andreas Gruenbacher
2005-02-02 16:25 ` [RFC][PATCH 3/3] Access Control Lists for /dev/pts Andreas Gruenbacher
2005-02-02 16:25 ` [RFC][PATCH 2/3] Access Control Lists for tmpfs Andreas Gruenbacher
2005-02-02 16:29 ` [RFC][PATCH 1/3] Generic infrastructure for acls Andreas Gruenbacher
2005-02-02 16:55 ` [RFC][PATCH 0/3] Access Control Lists for tmpfs and /dev/pts Christoph Hellwig
2005-02-02 17:37 ` Andreas Gruenbacher
2005-08-04 19:39 ` Catalin Patulea [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=Pine.LNX.4.60.0508041531460.11315@vv.carleton.ca \
--to=cat@vv.carleton.ca \
--cc=agruen@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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
all inboxes | Powered by JetHome®