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 is a socket created?
Can a socket have multiple ports?
How to find other end of unix socket connection?
Are sockets files?
Where is the socket located?
What is socket address with example?
How can I force a socket to send the data in its buffer?
What is socket address?
Why does it take so long to detect that the peer died?
Why do I get EPROTO from read()?
Why sockets are used?
Why do we need socket programming?
Are unix sockets faster than tcp?
Can multiple sockets use the same port?
What's the difference between impact sockets and regular sockets?
