OpenSSH startup issues - software related possibly?

Larry Hall (Cygwin) reply-to-list-only-lh@cygwin.com
Mon Aug 28 00:04:00 GMT 2006


<http://cygwin.com/acronyms/#TOFU>.  Reformatted.

Auteria Wallace Winzer Jr. wrote:
> --- "Larry Hall (Cygwin)"
> <reply-to-list-only-lh AT cygwin DOT com> wrote:
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> 
>> Auteria Wallace Winzer Jr. wrote:
>>> I've sent this thread a few times, yet I'm not
>> certain
>>> if it's getting to the group properly, therefore
>> I'm
>>> resending it again.
>>>
>>> I installed 1.5.21-1 on my new laptop. After
>>> configuring cygrunsrv and sshd I get the following
>>> error(s) which I've attached to this thread. the
>> files
>>> OpenSSH-sshd.log and sshd.log has the error
>>> information, and I've also attached cygcheck -svr.
>>
>> It's gotten here every time you've posted it:
>>
>> <http://cygwin.com/ml/cygwin/2006-08/msg00931.html>
>> <http://cygwin.com/ml/cygwin/2006-08/msg00959.html>
>> <http://cygwin.com/ml/cygwin/2006-08/msg00960.html>
>>
>> And, I sent my response after the first one:
>>
>> <http://cygwin.com/ml/cygwin/2006-08/msg00951.html>
>>
>> If you're really not sure whether your email is
>> getting through
>> to the list, the best way to check it is to look in
>> the email
>> archives, in this case for the month of August:
>>
>> <http://cygwin.com/ml/cygwin/2006-08/>
>>
>> If you see your email message there, the list has
>> seen it.
>> Otherwise, you know something has run a muck.  The
>> practice of
>> sending repeated messages to the list isn't
>> recommended.
>>
>> I've specifically cc'd you to be sure you get this
>> response, in
>> case you are not subscribed to the list for some
>> reason.
>>
 > I'm sorry for the repeated postings. I truly meant no
 > harm.
 >
 > I ran rebaseall as prescribed within the README file.
 > I did the following:
 >
 > Start->Run->D:\cygbin\usr\bin\ash.exe
 >
 > Within the window I ran /bin/rebaseall.
 >
 > After running it I relogged back into the Cygwin
 > window and restarted SSHD. I still have the same
 > problem.
 >
 > $ ssh -v -v awwjr@localhost
 > OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006
 > debug1: Reading configuration data /etc/ssh_config
 > debug2: ssh_connect: needpriv 0
 > debug1: Connecting to localhost [127.0.0.1] port 22.
 > debug1: Connection established.
 > debug1: identity file /home/awwjr/.ssh/identity type
 > -1
 > debug1: identity file /home/awwjr/.ssh/id_rsa type -1
 > debug1: identity file /home/awwjr/.ssh/id_dsa type -1
 > debug1: Remote protocol version 1.99, remote software
 > version OpenSSH_4.3
 > debug1: match: OpenSSH_4.3 pat OpenSSH*
 > debug1: Enabling compatibility mode for protocol 2.0
 > debug1: Local version string SSH-2.0-OpenSSH_4.3
 > debug2: fd 3 setting O_NONBLOCK
 > debug1: SSH2_MSG_KEXINIT sent
 >
 > That's where it stops. I have to Ctrl-C to get back to
 > the shell prompt.


This looks like a completely different problem to me.  You're
establishing a connection which means 'sshd' has successfully
started.  What happens if you just wait for 'ssh'?  Does it time
out?  You may need to start your 'sshd' in debug mode to see
what's happening on the server side to decipher this.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

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



More information about the Cygwin mailing list