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.

What is the difference between connected and unconnected sockets?

1 Answers  

---

When should I use shutdown()?

1 Answers   Wipro,

---

What is socket address?

0 Answers  

---

What is a sae socket?

0 Answers  

---

When will my application receive SIGPIPE?

1 Answers  

---

What is with the second parameter in bind()?

1 Answers  

---

of the socket? Does doing a connect() call affect the receive behaviour?

1 Answers  

---

Are sockets files?

0 Answers  

---

What exactly does SO_LINGER do?

1 Answers  

---

How can I write a multi-homed server?

0 Answers  

---

Can multiple clients connect to same socket?

0 Answers  

---

What is LILO?

2 Answers  

---