linux-kernel - Re: Security issues with local filesystem caching

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: <25083.1161796876@redhat.com>
Date:	Wed, 25 Oct 2006 18:21:16 +0100
From:	David Howells <dhowells@...hat.com>
To:	"Jeff V. Merkey" <jmerkey@...fmountaingroup.com>
Cc:	Nate Diller <nate.diller@...il.com>, sds@...ho.nsa.gov,
	jmorris@...ei.org, chrisw@...s-sol.org, selinux@...ho.nsa.gov,
	linux-kernel@...r.kernel.org, aviro@...hat.com,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: Security issues with local filesystem caching 

Jeff V. Merkey <jmerkey@...fmountaingroup.com> wrote:

> SELinux support addresses all of these issues for B1 level security quite
> well with mandatory access controls at the fs layers.  In fact, it works so
> well, when enabled you cannot even run apache on top of an FS unless
> configured properly.

How?  The problem I've got is that the caching code would be creating and
accessing files and directories with the wrong security context - that of the
calling process - and not a context suitable for sharing things in the cache
whilst protecting them from userspace as best we can.

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/