X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: sshd+ssh localhost connects, but don't reach the shell
Date: Tue, 30 May 2006 10:45:38 +0100
Message-ID: <02cb01c683cd$ceb5c0b0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BAY114-F6A42EB28A6B4CFE380D52BF920@phx.gbl>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On 30 May 2006 02:26, Vilar Camara wrote:

>>>> That's right, I had looked at it and completely forgot to mention it.
>>>> But my Event Log doesn't add anyting to our discussion: there are only
>>>>  log entries saying: `sshd' service started
>>>>  `sshd' service stopped, exit status: 0
>>>>  `sshd' service stopped, exit status: 255
>>>>  sshd: PID XXXX: Server listening on 0.0.0.0 port 22
>>>>  sshd: PID XXXX: Received signal 15; terminating
>>> 
>>> So it looks normal, as if everything is working fine.
>> 
>>   Eh?  Isn't signal 15 a SEGV?
> 
> SIGTERM, perhaps?

  Oh, yes, of course, silly me.  SEGV is (the infamous, much-dreaded) sig11.

> The event happens when I gracefully stop the service via
> "cygrunsrv -E sshd". It appears together with event "`sshd' service stopped,
> exit status: 255".

  Right, as you say, that all seems reasonable.

> debug3: Not a RSA1 key file /home/vilarnt/.ssh/id_rsa.
> debug2: key_type_from_name: unknown key type '-----BEGIN'
> debug3: key_read: missing keytype
> debug2: key_type_from_name: unknown key type 'Proc-Type:'
> debug3: key_read: missing keytype
> debug2: key_type_from_name: unknown key type 'DEK-Info:'
> debug3: key_read: missing keytype
> debug3: key_read: missing whitespace
> (previous line repeated many times)
> debug2: key_type_from_name: unknown key type '-----END'

  Ok, let's take a look at this.  Here's what mine looks like

-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,0..............B

xO.........................CENSORED!............................
...........................CENSORED!............................
            [ repeat many lines of base64 gibberish ]
...........................CENSORED!..........................BS
-----END RSA PRIVATE KEY----- 

  Does yours look the same way?  Does 'od -c <id_rsa' show any '\r' chars?

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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