linux-kernel - Re: [PATCH 3/3] CRED: Move the effective capabilities into the cred struct

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]

Date:	Thu, 20 Sep 2007 12:09:06 -0400
From:	Trond Myklebust <Trond.Myklebust@...app.com>
To:	casey@...aufler-ca.com
Cc:	Andrew Morgan <morgan@...nel.org>,
	David Howells <dhowells@...hat.com>, viro@....linux.org.uk,
	hch@...radead.org, sds@...ho.nsa.gov, linux-kernel@...r.kernel.org,
	selinux@...ho.nsa.gov, linux-security-module@...r.kernel.org
Subject: Re: [PATCH 3/3] CRED: Move the effective capabilities into the
	cred struct

On Thu, 2007-09-20 at 08:36 -0700, Casey Schaufler wrote:

> Ok, what can't be copied, and why can't it be copied?

In practice, no security information can be copied because the checks
are all made on the "current" pointer. There is no mechanism other than
'current' for passing security information around.

Trond
-
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/