The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Andreas Gruenbacher <agruen@suse.de>,
	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:25:24 +0000	[thread overview]
Message-ID: <20060110002523.GA22820@srcf.ucam.org> (raw)
In-Reply-To: <20060110001701.GA25690@vrfy.org>

On Tue, Jan 10, 2006 at 01:17:01AM +0100, Kay Sievers wrote:
> On Tue, Jan 10, 2006 at 12:07:58AM +0000, Matthew Garrett wrote:
> > 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.
> 
> That can be solved in the user session handling and not in the kernel.

Without killing every application that they've been left running? How? 
The only way I can think of is by checking open files against a 
blacklist, which seems, uhm, fragile.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2006-01-10  0:25 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
2006-01-10  0:17       ` Kay Sievers
2006-01-10  0:25         ` Matthew Garrett [this message]
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=20060110002523.GA22820@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=agruen@suse.de \
    --cc=akpm@osdl.org \
    --cc=kay.sievers@vrfy.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