| 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
| ||
|
Date: Thu, 02 Nov 2006 13:04:16 -0500 From: Stephen Smalley <sds@...ho.nsa.gov> To: Karl MacMillan <kmacmillan@...talrootkit.com> Cc: David Howells <dhowells@...hat.com>, jmorris@...ei.org, chrisw@...s-sol.org, selinux@...ho.nsa.gov, linux-kernel@...r.kernel.org, aviro@...hat.com Subject: Re: Security issues with local filesystem caching On Thu, 2006-11-02 at 11:29 -0500, Karl MacMillan wrote: > On Wed, 2006-11-01 at 12:45 -0500, Stephen Smalley wrote: > > On Wed, 2006-11-01 at 10:58 -0500, Karl MacMillan wrote: > > <snip> > > > > > fssid seems like the wrong name, though it does match the DAC concept. > > > This is really more general impersonation of another domain by the > > > kernel and might have other uses. > > > > NFS will want a fssid in order to have file access checks applied > > against the client process' SID if/when the client process' context > > becomes available. > > I was suggesting that it might be helpful if this applied to all checks > - not just file access - and would therefore need a different name. Not all checks (e.g. not when checking the ability of another task to send a signal to the task), but all checks where the task SID is used as the subject/source. -- Stephen Smalley National Security Agency - 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/
Powered by blists - more mailing lists