Re: OpenSSH
From: Brian K. White (brian_at_aljex.com)
Date: 09/22/03
- Previous message: Steve Camp: "Re: OpenSSH"
- In reply to: Brian K. White: "Re: OpenSSH"
- Next in thread: Bill Vermillion: "Re: OpenSSH"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 22 Sep 2003 01:29:06 -0700
This has nothing to do with the current "compressor war" that happens
to be labeled "Re: OpenSSH" rather, this is actually an OpenSSH
question...
I just built openssh 3.7.1p1 on a 5.0.7 box with the latest gnutools
This box had openssh 3.5p1 built-in before this, which worked fine.
I used it lots of times to connect, including many times just before
and during using the same box to build the new openssh. Connecting
from the same client IP, same client program, same options on the
server & client etc...
(putty, protocol 2 and blowfish forced in both client and server)
before building the new ssh, there was no delays during login. After
un-installing the old ssh:
custom -r SCO:ssh
and installing the new and starting it, connections experience a
rather long delay after answering the password prompt.
the login prompt appears immediately, but I beleive the way ssh works
that is supplied by the client not by the server like telnet. In any
even, my client is configured to already send a username and a private
key. The private key is rejected since I never copied it to this site,
and so immediately uppon connection I get a logging in as nnn message,
server rejected our key, and a password prompt all at once instantly.
This is normal. I answer the password prompt and 30-40 seconds later I
get a shell and everything is normal.
Yes it sounds like a common dns timeout.
except my ip does actually have a hostname, and the nameservers in
/etc/resolv.conf must be ok since I can lookup my ip and my hostname
instantly. (who -umx, ping, etc...) in any event, just for giggles I
added my IP to /etc/hosts just to see if it made a difference:
no difference.
not surprising since telnet & ftp and even ssh before replacing it
are/were fine.
Verified that the delay is not caused by any of the odd stuff I put in
/etc/profile (among other things, a who -m to detect real interactive
logins vs non-interactive sourcing.) by putting a
echo "/etc/profile starting...\c" ; read junk
at the top.
I had previously built 3.5p1 and applied the same chroot patch I
applied this time, and used the same (utter lack of) ./configure
options
I googled around to see if anyone alse experienced a delay at this
particular spot, but didn't find anything but the usual "make sure the
client ip can resolve by fixing resolv.conf or putting the ip in
/etc/hosts" (and making sure resolver is told to check hosts first)
I'm about to clean out this install and try jpr's (assuming I can
reach his ftp site this time) build, which does not have the chroot
patch and which does include various features (ssl etc...) that I
didn't include.
I'm assuming that this will all be moot soon, since openssh 3.5p1 was
bundled right in the base 5.0.7 install, that means sco will be
obliged to produce a 3.7 based update, which, presumable, will work
just as well as the original 3.5 unless the problem is in the 3.7 code
itself. I still need to build my own because I still need that chroot
patch but only for one site and maybe not for them for much longer.
- Previous message: Steve Camp: "Re: OpenSSH"
- In reply to: Brian K. White: "Re: OpenSSH"
- Next in thread: Bill Vermillion: "Re: OpenSSH"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
