11

I want syslog to run as a non-root user on my linux box. That makes it impossible for it to bind to port 514 - because that's a privileged port. Is there any way I can grant non-admin user "foo" the ability to listen on port 514?

4 Answers 4

10
setcap 'cap_net_bind_service=+ep' /path/to/syslogd

Requires a not-ancient linux kernel (2.6.24 or later)

3

You could configure rinetd (available in most, if not all, distribution's standard repositories) to listen on port 514 and forward connections to some other port (above 1024, say 1514). That way the non-privileged user process can listen on 1514 and rinetd will forward connections so it appears to be listening on 514.

This will only work for TCP connections though. If you need to support UDP (or anything else) this way as well as or instead of TCP, then you can use iptables translation rules to achieve the same effect.

1
  • Oh that was so easy. Here's a guide on how to do it in Ubuntu: ubuntugeek.com/…
    – Ivan
    Oct 18, 2011 at 17:33
2

Just found a very good discussion of this here: https://stackoverflow.com/questions/413807/is-there-a-way-for-non-root-processes-to-bind-to-privileged-ports-1024-on-li

Doesn't look easy

1
  • Good xref - didn't look very hard to me. Apr 18, 2010 at 0:03
2

Listen on an unprivileged port and use iptables dnat to redirect connections.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .