Re: PuTTY to OpenSSH, slow auth
- From: "Richard E. Silverman" <res@xxxxxxxx>
- Date: 27 Dec 2005 19:47:16 -0500
>>>>> "JB" == Jeff B <jbeardNo-Spam1185@xxxxxxxxxxxx> writes:
JB> Ross Crawford wrote:
>> Ross Crawford wrote: .... so the reverse DNS lookup was timing
>> out. So I added "UseDNS no" to sshd-config, and no more waiting!
>>
JB> it will also try both protocols(1,2) and the RSA/DSA and host
JB> authentications
I'm sorry, but none of this makes any sense. Neither the choice of SSH
protocol version nor the server key type can be "re-tried" in the course
of a single SSH connection; if either one doesn't work out for whatever
reason (e.g. the client has two keys for a host, and the one chosen
doesn't verify), the connection must be aborted. The only way what you're
describing could happen is if the client software made multiple SSH
connections in order to try these different parameters -- and PuTTY
doesn't appear to do that; I just tried it.
JB> so config the target host to use specifically that technique you
JB> used to create your pass-phrase and it will carve of some more
JB> time.
Passphrases have to do with user keys, which affect user authentication.
Above you mentioned issues with server authentication and protocol
version. Even if the issues you mentioned were valid, how could this
affect them in any way?
--
Richard Silverman
res@xxxxxxxx
.
- References:
- PuTTY to OpenSSH, slow auth
- From: Ross Crawford
- Re: PuTTY to OpenSSH, slow auth
- From: Ross Crawford
- Re: PuTTY to OpenSSH, slow auth
- From: Jeff B
- PuTTY to OpenSSH, slow auth
- Prev by Date: Controlling a second machine on the same desk
- Next by Date: Re: Monitor Incoming requests for ssh..?
- Previous by thread: Re: PuTTY to OpenSSH, slow auth
- Next by thread: restrict ssh access
- Index(es):
Relevant Pages
|