Interested to Buy Any Domain ? << Click Here >> for more details...
How can I bind() to a port number < 1024?
- 1 Answers
- 2473 Views
- I also Faced
- E-Mail Answers
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 are the types of sockets?
How can I tell when a socket is closed on the other end?
What is a socket file?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
How can I be sure that UDP messages are received in order?
Why do not my sockets close?
How can I find the full hostname (FQDN) of the system I am running on?
What is a socket address?
How can my client work through a firewall/proxy server?
How can I bind() to a port number < 1024?
Why does the sockets buffer fill up sooner than expected?
How many socket connections can a server handle?
Unix Commands 
