Hi, maximilian attems wrote: > On Wed, Aug 03, 2011 at 04:10:04PM +0200, Ralf Hildebrandt wrote:
>> After/deuring the installation of syslog-ng I found the attached trace >> in dmesg! > > oho, is that reproducible on 3.0 that you find in unstable? It looks like intended behavior. I guess the syslogd should be using CAP_SYSLOG these days. | commit ee24aebf | Author: Linus Torvalds <[email protected]> | Date: Thu Feb 10 17:53:55 2011 -0800 | | cap_syslog: accept CAP_SYS_ADMIN for now | | In commit ce6ada35bdf7 ("security: Define CAP_SYSLOG") Serge Hallyn | introduced CAP_SYSLOG, but broke backwards compatibility by no longer | accepting CAP_SYS_ADMIN as an override (it would cause a warning and | then reject the operation). | | Re-instate CAP_SYS_ADMIN - but keeping the warning - as an acceptable | capability until any legacy applications have been updated. There are | apparently applications out there that drop all capabilities except for | CAP_SYS_ADMIN in order to access the syslog. [...] | $ git name-rev --tags ee24aebf | ee24aebf tags/v2.6.38-rc5~46 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
