FS#22555 - Upcoming syslog breakage with kernel 2.6.38
Attached to Project:
Arch Linux
Opened by Xavier (shining) - Saturday, 22 January 2011, 19:20 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 31 March 2011, 07:11 GMT
Opened by Xavier (shining) - Saturday, 22 January 2011, 19:20 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 31 March 2011, 07:11 GMT
|
Details
The following patch introduces a new CAP_SYSLOG capability
required for syslog :
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ce6ada35bdf710d16582cc4869c26722547e6f11 So if this change remains in 2.6.38, libcap needs to be updated to 2.20 to be aware of the new cap : http://sites.google.com/site/fullycapable/release-notes-for-libcap And syslog-ng (and any other loggers?) needs to be patched to enable CAP_SYSLOG. See https://bugzilla.balabit.com/show_bug.cgi?id=108 I have a working patch for syslog-ng based on the two I found in the above bug report. |
This task depends upon
im actually testing 2.6.38-rc2 and this patch could come in handy ;)
I asked one syslog-ng dev to provide an updated patch, but he would like to find a solution which works both with old and new libcap.
My patch requires the new libcap.
I don't know if always trying to enable both caps (syslog and sys_admin) could work. Otherwise, we probably need kernel version checking from pld patch.
http://cvs.pld-linux.org/cgi-bin/cvsweb/packages/syslog-ng/cap_syslog.patch?rev=1.2
Attached a trivial port of the patch to 3.2.2 - the concerned code did not change, just the file paths did, so I had to apply the patch manually.
Tested on 2.6.36 ARCH and 2.6.38-rc2.
Arch lts kernel does not boot on that system, but anyway for versions < 2.6.34, the patch does not change anything.
https://aur.archlinux.org/packages.php?ID=45781
I tested it on kernel26, kernel26-lts and 2.6.38-rc2.
https://bugzilla.balabit.com/show_bug.cgi?id=108#c13
Apparently it's still under discussion and nothing has been merged yet.
http://groups.google.com/group/linux.kernel/browse_thread/thread/08abdca098b06ce3/2d295a9fdef3a404?#2d295a9fdef3a404
The upstream bug report is still open..