Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I would like to run applications I'm working on that binds to port numbers less than 1000 without requiring root access.

I'm using Linux Mint and have root access to set it up. I would ideally like to be able to do it over SSH.

Also happy hear if it isn't possible or I shouldn't be doing it, if that is the case.

EDIT: Mostly I'm happy to use higher port numbers for development, but Flash is expecting a socket policy on port 843. Currently I have to run the app as root and therefore I can't run it from my Makefile which is a PITA.

share|improve this question
7  
It isn't possible and you shouldn't be doing it :) (and if you have to do it, suexec and drop privileges after binding) –  Tzarium May 10 '11 at 10:48
    
@Tzarium - Appreciate that straight answer, although not what I wanted to hear :) Will sadly mark as accepted shortly. –  tarn May 10 '11 at 11:25
3  
@Tzarium It's not only possible but easy if your system supports filesystem capabilities. See @joeforker's setcap answer below. –  Gerald Combs May 10 '11 at 15:43
    
Authbind is also a good answer (from Simon below). This is very possible, in several different ways... –  Shane Madden May 10 '11 at 15:57
1  
show 1 more comment

4 Answers

up vote 33 down vote accepted

Another way of getting your daemon to respond to requests from a lower port number is to use iptables or similar to redirect a lower numbered port to the higher numbered port that your daemon is listening on.

share|improve this answer
    
Ok, that sounds like a workable workaround. I will look into that, Thanks. –  tarn May 10 '11 at 11:20
2  
That's what I've done before and it works fine: iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 843 -j REDIRECT --to-port 8430 (this redirects incoming connections on port 843 to port 8430) –  Andrew Lambert May 10 '11 at 17:07
5  
Unlike setcap, any program, not just the program you designated, will be able to listen on the unprivileged port. –  joeforker May 10 '11 at 17:14
add comment

Of course this is possible. You only need to give the binary CAP_NET_BIND_SERVICE.

sudo setcap cap_net_bind_service=ep some-binary

In Linux, the things root can do have been broken up into a set of capabilities. CAP_NET_BIND_SERVICE is the ability to bind to ports <= 1024.

It's probably even possible to use AppArmor, SELinux, or another Linux security module (LSM) to grant the program access to bind that one port specifically, but I think this would be a waste of time. Security is not really based on port numbers to the degree it was in the distant past.

share|improve this answer
    
Awesome, this is the answer I wanted. Will try that tonight. Thanks. –  tarn May 10 '11 at 23:43
    
A little bit of extra info on why this is the only approach that works: kneuro.net/cgi-bin/lxr/http/source/net/ipv4/… . PROT_SOCK=1024, and snum is the targeted port. –  BMDan May 14 '11 at 16:02
    
For bonus points: check out AccessFS for a real brain-twist. –  BMDan May 14 '11 at 16:08
add comment

I think there is a way to do it but im not 100% sure if this would work.

its the binding of the port that requires root, not the application's using it, so the below method may work but you need to have sudo access in the first place.

First you start your process as root user using sudo myApp, once the port has been bound you can switch the owner of the process to a non-privileged user.

share|improve this answer
1  
That will run the application as root and potentially expose the system to security risks. Works but the iptables redirect is more secure. –  HampusLi May 10 '11 at 12:16
4  
This is the way almost all daemons work; root starts them (init), they open the necessary ports, then chance their UID/GID to an unprivileged user. –  Chris S May 10 '11 at 13:07
add comment

I dimly remember a library called "authbind" that does what you need, by wrapping the bind() system call (via a LD_PRELOAD library), and, if a privileged port is requested, spawning a setuid root program that receives a copy of the file descriptor, then verifies the application is indeed permitted to bind to the port, performs the bind() and exits.

Not sure about the project status, but the method should be fairly straightforward to (re)implement if required.

share|improve this answer
    
I would say authbind is obsolete on Linux compared to capabilities or AppArmor/SELinux/other Linux security modules. –  joeforker May 10 '11 at 16:03
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.