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
What's better 6pt or 12pt sockets?
How can I set the timeout for the connect() system call?
How does a socket work?
What is socket programming in java?
Is a socket a file?
Why do we need socket programming?
What is a socket set used for?
What is the function of socket?
How is a socket created?
How to find other end of unix socket connection?
How are unix domain sockets implemented?
Whats the difference between select() and poll()?
Can a single socket port be used for multiple applications?
What is a sae socket?
What is the difference between read() and recv()?