Messages in this thread | | | Date | Thu, 3 Feb 2011 10:54:25 -0500 | From | Nick Bowler <> | Subject | Re: CAP_SYSLOG, 2.6.38 and user space |
| |
On 2011-02-03 15:32 +0000, Serge E. Hallyn wrote: > At 2.6.39 or 2.6.40, let's add a sysctl which defaults to 0. When > 0, refuse if cap_sys_admin, if 1, then allow.
This had better default to 1, since that's the "don't break working systems" setting. Users (more likely, distributions) can set it to 0 when they have new enough userspace.
> This will allow users to acknowledge (permanently, if they must, using > /etc/sysctl.conf) that they've seen the syslog message about > cap_sys_admin being deprecated for syslog.
Why should the user need to acknowledge anything in order for their system to not be broken? What are they supposed to do otherwise?
-- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
| |