| 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: Fri, 27 Jan 2012 12:05:52 -0800 From: Kees Cook <kees@...ntu.com> To: Casey Schaufler <casey@...aufler-ca.com> Cc: linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, John Johansen <john.johansen@...onical.com> Subject: Re: [PATCH 0/4] AppArmor: refactor securityfs to use structures Hi Casey, On Fri, Jan 27, 2012 at 10:54:12AM -0800, Casey Schaufler wrote: > On 1/26/2012 4:29 PM, Kees Cook wrote: > >This is the ground-work for expanding the AppArmor securityfs to include > >useful information that the userspace tools can more easily interact with. > >Presently, this is only static information about the state of AppArmor. > > If you're making changes for securityfs do you suppose that > you might do all of us LSM developers a huge favor and add an > entry that reports the active LSM? It's something that has been > on my todo list for ages and would make everyone's life so much > easier. /sys/kernel/security/LSM which contains the name of the > active LSM would be very handy. Should that appear in the securityfs? Normally one can just mount it and look to see what's in there. And, I'm nervous to add a file here without a good LSM stacking plan yet. I'd hate to create another interface that needs to be redefined later. :) -Kees -- Kees Cook -- 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