| 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: <20060801152503.GA2825@slug> Date: Tue, 1 Aug 2006 17:25:03 +0200 From: Frederik Deweerdt <deweerdt@...e.fr> To: Amit Gud <agud@...hat.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [RFC] [PATCH] sysctl for the latecomers On Tue, Aug 01, 2006 at 10:49:20AM -0400, Amit Gud wrote: > /etc/sysctl.conf values are of no use to kernel modules that are inserted > after init scripts call sysctl for the values in /etc/sysctl.conf > > For modules to use the values stored in the file /etc/sysctl.conf, sysctl > kernel code can keep record of 'limited' values, for sysctl entries which > haven't been registered yet. During registration, sysctl code can check > against the stored values and call the appropriate strategy and proc_handler > routines if a match is found. > > Attached patch does just that. This patch is NOT tested and is just to get > opinions, if something like this is a right way of addressing this problem. > > Hi, One strange behaviour that comes to mind is the following: 1. I boot my machine so that it doesn't load module X 2. I modify /etc/sysctl.conf and I remove a line affecting module X 3. I modprobe X Wouldn't the fact that the sysctl directive is applied anyway be a bit misleading? Regards, Frederik - 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