Hi Stephen,
The solution is to not use inetd at all. Start sshd in your system start
up, such as the /etc/ec.d/inet.d directory on Linux. As you know inetd is
what runs not the servers it monitors ports for. When inetd gets a
request for a specific port it starts up the appropriate server. Since
ssh has to generate a 1024 byte key everytime it starts this takes a
while and is also know to timeout when used with inetd. You can shorted
the key length, but then the key is easier to break, so don't use inetd.
Carl
On 03-Apr-01 Stephen Morley wrote:
> This question is probably more about inet than ssh, but does anyone
> know how
> to get a connection faster. Sometime the system takes over 60s to
> connect
> even though it is not particularly busy.
>
> Stephen
------------------------------------------------------------------------
E-Mail: Carl J. Nobile <[EMAIL PROTECTED]>
Date: 03-Apr-01 Phone: 315-453-2912 Ex. 5336
Time: 10:55:48 Fax: 315-479-0859
Software Engineering Group -- AppliedTheory Corp.
224 Harrison Street, 6th Floor, Syracuse, NY 13202
------------------------------------------------------------------------
