On Thursday, July 28, 2005, at 02:34 am, S. Zachariah Sprackett wrote:
While some protocols do this, this is not necessary. SMTP
for example can take exceedingly long times to complete. SSH is also
often used for extended sessions. The communication all happens on a
well known destination port (ie: 25 or 22). It's really not necessary
to use random ports for these types of applications and it doesn't buy
you anything. Often, in fact, it makes your life more difficult as
firewalls are more difficult to configure.
I'm having difficulty with this one. If SSH is done thru only one port,
1. The session is continually being interrupted by others wanting to
login via SSH.
2. Only one login is allowed.
I suppose it is possible for SSH to do multiple sessions but why ignore
a well-known, and therefore well-bugged, protocol?
BTW, the little guy listening is called a daemon. The reason he's said
to be listening is because he is using synchronous input protocol and
must wait until there is input.