From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch 0/2] Tmpfs acls
Date: Tue, 10 Jan 2006 00:07:58 +0000 [thread overview]
Message-ID: <20060110000758.GA22399@srcf.ucam.org> (raw)
In-Reply-To: <200601100059.47317.agruen@suse.de>
On Tue, Jan 10, 2006 at 12:59:46AM +0100, Andreas Gruenbacher wrote:
> On Monday 09 January 2006 00:34, Matthew Garrett wrote:
> > Hmm. Do you have any infrastructure for revoking open file descriptors
> > when a user logs out?
>
> Open file descriptors have nothing to do with it. The device permissions are
> set by different pam modules on different distributions (pam_console,
> pam_resmgr).
Right. But what stops a user writing an application that opens a device,
hangs around after the user logs out and then provides access to the
user when logged in remotely?
Handwavy problem scenario - user A logs in, is given access to the
soundcard. Starts running a program that when given appropriate signals
will record from the system microphone. Logs out. Waits for user B, who
he suspects is having an affair with his wife, and then monitors any
conversations that user B has. ACLs on their own don't seem to solve
this any more than just statically assigning group membership to users.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-01-10 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 23:23 [patch 0/2] Tmpfs acls Andreas Gruenbacher
2006-01-08 23:34 ` Matthew Garrett
2006-01-09 23:59 ` Andreas Gruenbacher
2006-01-10 0:07 ` Matthew Garrett [this message]
2006-01-10 0:17 ` Kay Sievers
2006-01-10 0:25 ` Matthew Garrett
2006-01-10 0:28 ` Alan Cox
2006-01-10 12:01 ` Gabor Gombas
-- strict thread matches above, loose matches on Subject: below --
2006-09-01 22:14 Andreas Gruenbacher
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=20060110000758.GA22399@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=torvalds@osdl.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