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: Wed, 4 Feb 2015 12:12:04 -0600 (CST) From: Christoph Lameter <cl@...ux.com> To: "Serge E. Hallyn" <serge@...lyn.com> cc: "Andrew G. Morgan" <morgan@...nel.org>, Andy Lutomirski <luto@...capital.net>, Serge Hallyn <serge.hallyn@...ntu.com>, Serge Hallyn <serge.hallyn@...onical.com>, Jonathan Corbet <corbet@....net>, Aaron Jones <aaronmdjones@...il.com>, Ted Ts'o <tytso@....edu>, LSM List <linux-security-module@...r.kernel.org>, lkml <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...uxfoundation.org> Subject: Re: [capabilities] Allow normal inheritance for a configurable set of capabilities On Wed, 4 Feb 2015, Serge E. Hallyn wrote: > Ok this is all sounding too magic for my tastes. My original suggestion > was for an actual new capability set, pA, empty by default. You can > add bits to it using prctl if ns_capable(CAP_SETPCAP) and all the new bits are > in your pE. Once set, they stay until they are removed using prctl. At > exec, pA' = pA, and fI |= pA (after reading fI from disk but before > calculating pI'). Sounds good. I think we cannot avoid the additional capability set in the cred structure since otherwise the regular ("crippled") inheritance bits may be modified and then not passed on correctly. -- 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