| 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
| ||
|
Message-ID: <20070514135110.GC5877@suse.de>
Date: Mon, 14 May 2007 06:51:10 -0700
From: John Johansen <jjohansen@...e.de>
To: jjohansen@...e.de
Cc: linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [RFD Patch 0/4] AppArmor - Don't pass NULL nameidata to vfs_create/lookup/permission IOPs
sigh, and with the intoductory text attached
This post is a request for discussion on creating a second minimal
nameidata struct to eliminate conditionally passing of vfsmounts
to the LSM.
It contains a series of patches that apply on top of the AppArmor
patch series. A previous version of these patches was posted by
Andreas Gruenbacher on April 16, and the issues raised then have been
addressed.
To remove conditionally passing of vfsmounts to the LSM, a nameidata
struct can be instantiated in the nfsd and mqueue filesystems. This
however results in useless information being passed down, as not
all fields in the nameidata struct will be meaingful. The nameidata
struct is split creating struct nameidata2 that contains only the fields
that will carry meaningful information.
The creation of the nameidata2 struct raises the possibility of
replacing the current dentry, vfsmount argument pairs in the
vfs and lsm patches with a single nameidata2 argument although these
patches do not currently do this.
A tarball of these patches and the AppArmor kernel patches are
available at:
http://forgeftp.novell.com//apparmor/LKML_Submission-May_07/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists