This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: sshd as service without /usr/bin being in the system path.


I diffed the two files you provided and noticed this:

ssh-fail.txt:
debug1: Remote protocol version 1.99, remote software version
OpenSSH_2.9p2
debug1: match: OpenSSH_2.9p2 pat OpenSSH_2.*,OpenSSH_3.0*,OpenSSH_3.1*

ssh-succeed.txt:
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.6.1p1
debug1: match: OpenSSH_3.6.1p1 pat OpenSSH*

So apparently, you're not starting the same version of sshd when you
boot as when you manually start the service.  Weird.

Also, I noticed this:

ssh-fail.txt:
debug1: Host 'devtestw2k' is known and matches the DSA host key.

ssh-succeed.txt:
debug1: Host 'devtestw2k' is known and matches the RSA host key.

That is, the failing case is finding a DSA host key, while the
succeeding case is finding an RSA host key.  This makes me wonder
whether the sshd process started at boot is even using the same /etc
directory.

Dave

Steve Fairbairn wrote:
> 
> I have attached ssh -v logs from both a failed connection and a successful
> one.  If anyone has any suggestions, I'd be most grateful.

--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]