linux-kernel - Re: [PATCH 00/59] Introduce credentials

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <21723.1219847044@redhat.com>
Date:	Wed, 27 Aug 2008 15:24:04 +0100
From:	David Howells <dhowells@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	dhowells@...hat.com, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org
Subject: Re: [PATCH 00/59] Introduce credentials

Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > The wrappings are there to make the implementation of copy-on-write
> > credentials easier.
> 
> What do we get from copy-on-write credentials?

By credentials, I mean: UID, GID, EUID, EGID, SUID, SGID, FSUID, FSGID,
supplementary groups, LSM module context, all four capabilities masks, keyring
subscriptions.

We get a number of things:

 (1) Multiple credential changes all happen simultaneously (setresuid() for
     example).  The new set of credentials is committed with a single RCU
     assignment.

 (2) Some simplification of capabilities handling functions.

 (3) Because the credentials are detached, execve() credential recalculation is
     simplified.  We set up a new set of the credentials we want in advance and
     only commit at the last possibly moment.  Not only that, the credentials
     are committed in one go, rather than being committed piecemeal.

 (4) execve() no longer leaves the credential state incompletely restored if it
     returns an error.

 (5) Other tasks observing an exec'ing process won't see a partially changed
     state; nor will they see a state that gets reverted.

 (6) For one task to read another's credentials, it only needs to keep hold of
     the RCU lock and can drop any spinlocks it has sooner.  Furthermore, it
     can get a reference on that other task's cred struct and drop the RCU lock
     too.

 (7) Because the credentials are detached, it makes it much easier to override
     all of them _without_ affecting how another task acts upon this one.  This
     cleans up do_coredump() and sys_faccessat().  It may help NFSD, especially
     when it comes to supporting SELinux labelling over NFS, and it helps me
     with local caching of network filesystems.

> I've never seen credentials of any kind showing in profiles so why do we
> need this ?

I'm not sure what you mean by that.  Are you talking about profiling as in with
gprof or oprofile, or profiles as in user profiles?

Anyway; my primary interest is this: I want to be able to do local caching of
network filesystems.  One method of doing this is to create a file on disk to
cache each AFS/NFS/CIFS/whatever file I'm asked to cache.  However, I may be
attempting to access disk in the context of the process that invoked the netfs,
but this may have an inappropriate set of credentials for accessing the local
cache.

What Al Viro and Christoph Hellwig would like is for the subjective cred
pointer to be handed to vfs_mkdir() and suchlike and to percolate down through
the filesystems.  Currently I have something that approximates a subjective
pointer and an objective pointer in the task_struct in place of the removed
creds.  Ideally, the subjective pointer ought to be dispensed with and the
appropriate set of creds be handed down instead.  XFS, for example, is already
set up to do this.  I have patches to do most of this, but there are ~150 of
them and they stand at ~5.5MB in size.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/