| 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: <alpine.DEB.1.10.0901072350480.31038@asgard.lang.hm> Date: Wed, 7 Jan 2009 23:52:29 -0800 (PST) From: david@...g.hm To: Andi Kleen <andi@...stfloor.org> cc: Michael Stone <michael@...top.org>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: RFC: Network privilege separation. On Thu, 8 Jan 2009, Andi Kleen wrote: > On Wed, Jan 07, 2009 at 09:31:11PM -0500, Michael Stone wrote: >> -- if it's different from Joe User's regular uid, then where did it come >> from and how is Joe going to clean it up when he no longer needs it? > > You always create joe-nonet one when you create joe > > Now writing to joe's files: you can either use ACLs or do everything > through group accesses (it's very common to have a "joe" group for this > purpose for each user) > > But perhaps it's a good idea to not allow writing to all of Joe's > files by those "no network" processes too. It at least sounds like > that might be useful to combine. there are times when that would be nice, but it's also a bit of a pain to have to change the permissions so that joe-nonet can access all the files that joe can access (they will have to be set with the correct group ownership and hope that there wasn't a reason to use any other group) David Lang -- 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