Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Oct 2001 00:09:39 -0700
From:      "Crist J. Clark" <cristjc@earthlink.net>
To:        Jim Conner <jconner@enterit.com>
Cc:        Kris Kennaway <kris@obsecurity.org>, freebsd-questions@FreeBSD.ORG
Subject:   Re: SSH - anyone else had this problem?
Message-ID:  <20011014000939.A321@blossom.cjclark.org>
In-Reply-To: <5.1.0.14.0.20011014012951.02b85028@mail.enterit.com>; from jconner@enterit.com on Sun, Oct 14, 2001 at 01:33:44AM -0400
References:  <5.1.0.14.0.20011013131959.02d81150@mail.enterit.com> <5.1.0.14.0.20011013131959.02d81150@mail.enterit.com> <20011013145844.B74148@xor.obsecurity.org> <5.1.0.14.0.20011014012951.02b85028@mail.enterit.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 14, 2001 at 01:33:44AM -0400, Jim Conner wrote:
> At 14:58 10.13.2001 -0700, Kris Kennaway wrote:
> >On Sat, Oct 13, 2001 at 01:26:24PM -0400, Jim Conner wrote:
> > > I just installed 4.3 Current very vanilla install including with
> > > ssh.  Using SSH as my main way of remote administration I notcied after
> > > about three days of the machine being up that after a client authenticates
> > > it takes nearly a minute for the shell to start.  I figured this might be
> > > because reverse lookups were not working properly.  When I ran a verbose
> > > client I noticed that reverse lookups occur just after the client enters
> > > his/her login name and cr's.  However, once a client inputs his/her passwd
> > > and cr's this is when the problem occurs.  So I don't think its reverse ns
> > > lookups.
> >
> >Yes, it probably is reverse DNS lookup.
> 
> It's not reverse lookups.  I see in the logs that the reverse lookup is 
> working.  I watched during a verbose output of the client (and watching the 
> log on the server side) when reverse lookup occurs.  I see that reverse 
> lookup occurs just after the client enters their username and presses 
> enter.  The problem I'm seeing occurs *after* the user puts his/her 
> password in *after* the lookup has already successfully occurred.  It is 
> something else.  Unless you can explain to me what other reverse lookup it 
> seems to be doing after it has already successfully looked up the ptr.

It still may be lookup issuse from the DISPLAY name. Are you doing X11
forwarding? What happens if you try it without X11 forwarding,

  $ ssh -x -v -v remote-host

And see if it still does it.
-- 
Crist J. Clark                     |     cjclark@alum.mit.edu
                                   |     cjclark@jhu.edu
http://people.freebsd.org/~cjc/    |     cjc@freebsd.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011014000939.A321>