Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / 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 |
Post New Answer View All Answers
How many socket connections can a server handle?
What is socket programming in java?
What is difference between socket and websocket?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
Are unix sockets faster than tcp?
What is the function of socket?
What is a socket api?
How many sockets can a port have?
What pieces of information make up a socket?
Why do I get EPROTO from read()?
What are the types of sockets?
What is socket address with example?
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?
Why do we need sockets?
Where is the socket located?
