Skip to contentSkip to conversation

Allow capabilities for syslog-ng

PATCH New Sven Vermeulen 2 participants 2 messages Oct 21, 2013 – Nov 13, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Allow capabilities for syslog-ng

The syslog-ng logger has (build-optional) support for capabilities. If capabilities support is enabled, running it without setcap/getcap permissions gives the following upon start:

* Starting syslog-ng ...
syslog-ng: Error setting capabilities, capability management disabled; error='Permission denied' [ ok ]

Granting only setcap (initial AVC seen) does not fully help either:

* Starting syslog-ng ...
Error managing capability set, cap_set_proc returned an error;

With setcap and getcap enabled, syslog-ng starts and functions fine.

See also https://bugs.gentoo.org/show_bug.cgi?id=488718

---
 policy/modules/system/logging.te | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
policy/modules/system/logging.te +1 -1
index 59b04c1..d7e857e 100644
@@ -361,7 +361,7 @@ dontaudit syslogd_t self:capability sys_tty_config;
 # setrlimit for syslog-ng
 # getsched for syslog-ng
 # setsched for rsyslog
-allow syslogd_t self:process { signal_perms setpgid setrlimit getsched setsched };
+allow syslogd_t self:process { getcap setcap signal_perms setpgid setrlimit getsched setsched };
 # receive messages to be logged
 allow syslogd_t self:unix_dgram_socket create_socket_perms;
 allow syslogd_t self:unix_stream_socket create_stream_socket_perms;
Signature · 1 line
1.8.1.5
#1 lore raw

PATCH 1/1 Allow capabilities for syslog-ng

Quoted 28 lines · Sven Vermeulen

The syslog-ng logger has (build-optional) support for capabilities. If capabilities support is enabled, running it without setcap/getcap permissions gives the following upon start:

* Starting syslog-ng ...
syslog-ng: Error setting capabilities, capability management disabled; error='Permission denied' [ ok ]

Granting only setcap (initial AVC seen) does not fully help either:

* Starting syslog-ng ...
Error managing capability set, cap_set_proc returned an error;

With setcap and getcap enabled, syslog-ng starts and functions fine.

See also https://bugs.gentoo.org/show_bug.cgi?id=488718

---
 policy/modules/system/logging.te | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
policy/modules/system/logging.te +0 -0
index 59b04c1..d7e857e 100644

policy/modules/system/logging.te dontaudit syslogd_t self:capability sys_tty_config; · line 367

Quoted 8 lines
policy/modules/system/logging.te +1 -1
@@ -361,7 +361,7 @@ dontaudit syslogd_t self:capability sys_tty_config;
 # setrlimit for syslog-ng
 # getsched for syslog-ng
 # setsched for rsyslog
-allow syslogd_t self:process { signal_perms setpgid setrlimit getsched setsched };
+allow syslogd_t self:process { getcap setcap signal_perms setpgid setrlimit getsched setsched };
 # receive messages to be logged
 allow syslogd_t self:unix_dgram_socket create_socket_perms;
 allow syslogd_t self:unix_stream_socket create_stream_socket_perms;

Merged.

--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com