mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Cc: James Morris <jmorris@namei.org>, Kay Sievers <kay.sievers@vrfy.org>
Subject: [patch 0/2] Tmpfs acls
Date: Sat, 02 Sep 2006 00:14:21 +0200	[thread overview]
Message-ID: <20060901221421.968954146@winden.suse.de> (raw)

This is a refresh of the patches we have to support POSIX ACLs on tmpfs,
with the request for inclusion.

The patches solve the following problem: We want to grant access to
devices based on who is logged in from where, etc. This includes
switching back and forth between multiple user sessions, etc.

Using ACLs to define device access for logged-in users gives us all the
flexibility we need in order to fully solve the problem.

Device special files nowadays usually live on tmpfs, hence tmpfs ACLs.

Different distros have come up with solutions that solve the problem to
different degrees: SUSE uses a resource manager which tracks login
sessions and sets ACLs on device inodes as appropriate. RedHat uses
pam_console, which changes the primary file ownership to the logged-in
user. Others use a set of groups that users must be in in order to be
granted the appropriate accesses.

The freedesktop.org project plans to implement a combination of a
console-tracker and a HAL-device-list based solution to grant access to
devices to users, and more distros will likely follow this approach.

-

These patches have first been posted here on 2 February 2005, and again
on 8 January 2006. We have been shipping them in SLES9 and SLES10 with
no problems reported.  The previous submission is archived here:

   http://lkml.org/lkml/2006/1/8/229
   http://lkml.org/lkml/2006/1/8/230
   http://lkml.org/lkml/2006/1/8/231

Could the patches please get included this time?

Andrew, is putting them in -mm for a while fine with you?

Thanks,
Andreas

--
Andreas Gruenbacher <agruen@suse.de>
Novell / SUSE Labs

-- 
VGER BF report: U 0.5

             reply	other threads:[~2006-09-01 21:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 22:14 Andreas Gruenbacher [this message]
2006-09-01 22:14 ` Generic infrastructure for acls Andreas Gruenbacher
2006-09-01 21:44   ` Andrew Morton
2006-09-01 22:32     ` Andreas Gruenbacher
2006-09-06 16:40     ` Andreas Gruenbacher
2006-09-06 20:06       ` Randy.Dunlap
2006-09-06  6:54   ` Jan Engelhardt
2006-09-01 22:14 ` Access Control Lists for tmpfs Andreas Gruenbacher
2006-09-01 21:52   ` Andrew Morton
2006-09-02  7:24     ` Arjan van de Ven
2006-09-05 19:07   ` Andrew Morton
2006-09-06 16:40     ` Andreas Gruenbacher
2006-09-06  7:02   ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
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
2006-01-10  0:28         ` Alan Cox
2006-01-10 12:01       ` Gabor Gombas

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=20060901221421.968954146@winden.suse.de \
    --to=agruen@suse.de \
    --cc=akpm@osdl.org \
    --cc=jmorris@namei.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome