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, 01 Jul 2010 15:57:55 -0400 From: Stephen Smalley <sds@...ho.nsa.gov> To: "Serge E. Hallyn" <serge@...lyn.com> Cc: Kees Cook <kees.cook@...onical.com>, James Morris <jmorris@...ei.org>, Christoph Hellwig <hch@...radead.org>, linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/2] Yama: add PTRACE exception tracking On Thu, 2010-07-01 at 14:41 -0500, Serge E. Hallyn wrote: > Quoting Kees Cook (kees.cook@...onical.com): > > > > I still think simple chaining is the way to go. I want to review the > > > > earlier discussions first (I think Serge said it was in 2004ish?) before I > > > > write up anything. There is, I think, one sticking point, which is > > > > /proc/self/attr/current, but beyond that, I think some simple > > > > reorganization of LSM initialization routines and a list that security_* > > > > walks would be sufficient. > > > > > > In the past, output results for each LSM were simply split by \n or a : > > > or something, and input was prepended by the LSM name. > > > > This doesn't appear to be true anymore. Looking at the fs/proc/base.c and > > security/selinux/hooks.c code, there is no checking for a prepended LSM > > name. Maybe that's the first chaining limitation -- you can't chain 2 LSMs > > that both declare setprocattr hooks. > > No no, Stephen and I were talking about in the stacker patchset, again > around 2004-2005. Never went upstream (per 2005 or 2006 ksummit > agreement). Patch series was also available from: http://sourceforge.net/projects/lsm-stacker/files/ Looks like it was last updated in 2006. -- 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