How can I bind() to a port number < 1024?
Answer / chaitanya
The restriction on access to ports < 1024 is part of a (fairly weak) security scheme particular to UNIX. The intention is that servers (for example rlogind, rshd) can check the port number of the client, and if it is < 1024, assume the request has been properly authorised at the client end.
The practical upshot of this, is that binding a port number < 1024 is reserved to processes having an effective UID == root.
This can, occasionally, itself present a security problem, e.g. when a server process needs to bind a well-known port, but does not itself need root access (news servers, for example). This is often solved by creating a small program which simply binds the socket, then restores the real userid and exec()s the real server. This program can then be made setuid root.
| Is This Answer Correct ? | 0 Yes | 0 No |
What exactly does SO_REUSEADDR do?
What is with the second parameter in bind()?
How are unix domain sockets implemented?
What is difference between socket () and serversocket () class?
How come select says there is data, but read returns zero?
What is the difference between a socket and a port?
When should I use UDP instead of TCP?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
What is a socket address?
What pieces of information make up a socket?
If bind() fails, what should I do with the socket descriptor?
What is a socket connection?