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 |
How do I properly close a socket?
If bind() fails, what should I do with the socket descriptor?
of the socket? Does doing a connect() call affect the receive behaviour?
Can multiple sockets use the same port?
How do I get my server to find out the clients address / host- name?
Why do we need socket programming?
How does a socket work?
What is the difference between a socket and a port?
How can my client work through a firewall/proxy server?
How come I get address already in use from bind()?
How do I get the port number for a given service?
What is active unix domain sockets?