X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,UNPARSEABLE_RELAY
X-Spam-Check-By:	sourceware.org
In-Reply-To:	<20081216053657.GA1340@tomas>
References:	<OFB9B7CEEA DOT 015F9FE3-ONC1257520 DOT 003D6956-C1257520 DOT 003D749A AT nbg DOT sdv DOT spb DOT de> <20081215135047 DOT GU32197 AT calimero DOT vinschen DOT de> <OF9DDDB5A1 DOT 3FF00E83-ONC1257520 DOT 004F6858-C1257520 DOT 005163AC AT nbg DOT sdv DOT spb DOT de> <20081216053657 DOT GA1340 AT tomas>
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
X-KeepSent:	B6A35DEB:E5E38AFD-C1257521:002F9DE3; type=4; name=$KeepSent
Message-ID:	<OFB6A35DEB.E5E38AFD-ONC1257521.002F9DE3-C1257521.00302437@nbg.sdv.spb.de>
From:	Carsten DOT Porzler AT spb DOT de
Date:	Tue, 16 Dec 2008 09:45:56 +0100
X-SafeGuard_MailGateway:	Version: 5.30.1.7110 SGMG (smtpd: 6.71.2.3) Date: 20081216084557Z
Subject:	=?ISO-8859-15?Q?Re:_SSH_V=2E5=2E1_with_Cygwin1=2Edll_1=2E7=2E0=280?= =?ISO-8859-15?Q?=2E189/5/3=29_2008-12-09:_Very__large__logon_times?= =?ISO-8859-15?Q?=2E=2E=2E?=
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id mBGCl0TE014192

Hello, Tomás,

I do not think there is a problem with DNS lookup timeouts!

If it would be so, we must also have the problem with the cygwin prior to 
2008-06-18.

Furthermore, the problem does not occur, if we use local Windows users in 
our passwd file.

Looking at all facts I reported, I have to conclude that the cause for the 
behaviour is in the cygwin environment.

Thanks and 

best regards

Carsten Porzler



> > Hello, Corinna,
> > 
> > "large" logon time means 45 - 66 secs during public key authentication 

> > from viewing the banner text until an simple command has been excuted 
> > (e.g. "uname -a").
> 
> Hm. This looks a lot like a DNS lookup timeout. Is there anything in the
> process where the client would have to  try a DNS lookup? Known hosts
> (by name)? Tcpwrappers? Logging?
> 
> (Thanks, Corinna for the TOFU :-)
> 
> Regards
> - -- tomás
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFJRz55Bcgs9XrR2kYRArywAJ9tRndCV3NKtrMJctixNLLqvnRsIgCeOn9j
> xdbtcefQirCMzKylVdH97a8=
> =m5mZ
> -----END PGP SIGNATURE-----
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -