linux-kernel - Re: sysctl in 2.6.24.2 excludes unapproved files from /proc/sys?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200803010937.m219b3or011970@betty.it.uc3m.es>
Date:	Sat, 1 Mar 2008 10:37:03 +0100 (CET)
From:	"Peter T. Breuer" <ptb@....it.uc3m.es>
To:	Alexey Dobriyan <adobriyan@...il.com>
CC:	linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: sysctl in 2.6.24.2 excludes unapproved files from
 /proc/sys?

"Also sprach Alexey Dobriyan:"
> 
> If I understand you correcty, the answer is drop '.ctl_name' bits from
> new sysctls and make sure common parts of tables match the ones
> in mainline.

YES! Setting .ctl_name to 0 on _every_ _single_ _item_ of my sub-hierarchy
did the trick. Thank you, thank you, thank you.

And how does it know when it gets to the end of a list held as
consecutive entries in an array now? One always used to set .ctl_name
to zero for that marker!

I'd better zero absolutely everything at array end.

Thanks again. I was looking at the documentation for configfs (it
exists!) and muttering "this is way too hard and unsuitable anyway",
and sysfs ("this is just not appropriate"). Sysctl is definitely
the right thing to do for me .. modulo that I would like some finer
control, at my choice, of over when things appear and disappear.

Peter
--
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/