| 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: <20110520151731.GT25448@outflux.net> Date: Fri, 20 May 2011 08:17:31 -0700 From: Kees Cook <kees.cook@...onical.com> To: Greg KH <gregkh@...e.de> Cc: Vasiliy Kulikov <segoon@...nwall.com>, linux-kernel@...r.kernel.org, Eugene Teo <eugeneteo@...il.com> Subject: Re: [RFC] add mount options to sysfs Hi Greg, On Fri, May 20, 2011 at 06:54:24AM -0700, Greg KH wrote: > That's the question for you, we would be changing the kernel/user api > here, and odds are, something will break. I feel like this is going in circles. :) Adding this feature (with no changes to the defaults) will: - not break anything in the standard case - allow a system owner to locally choose the DAC perms on the mounts The question is about providing a temporal buffer between when a flaw is found in sysfs or debugfs and when the fix for it gets to the system owner. This, of course, presupposes that flaws are even publicly discovered in the first place. It gives paranoid system owners the option to lock down sysfs and debugfs from non-root users while still having them mounted without needing to make rather non-standard changes to boot time scripts beyond changing the fstab. Given that things like tmpfs support these options, it seems only sane to suppor them here too. -Kees -- Kees Cook Ubuntu Security Team -- 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