Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Reply-To: Cygwin List <cygwin@cygwin.com>
Message-Id: <6.1.0.6.0.20041019085857.04434bb8@pop.prospeed.net>
X-Sender: 
Date: Tue, 19 Oct 2004 09:01:32 -0400
To: Wayne A McAuliffe <waynemc@au1.ibm.com>, cygwin@cygwin.com
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
Subject: Re: ssh.exe 3.7.1p1:  crashing with STATUS_ACCESS_VIOLATION error @ 0x016E65A8
In-Reply-To: <loom.20041019T012057-477@post.gmane.org>
References: <loom.20041019T012057-477@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 12:36 AM 10/19/2004, you wrote:
>Hello,
>
>I've not seen ssh.exe abort in this fashion before.
>
>I have a product which uses ssh without any problems (on about 2,500 servers),
>but one troublesome server throws this exception.
>
>** The command line is:
>ssh -vvv -o 'stricthostkeychecking=no' -i authorized_keys2 -l myuser AServer ..
>
>** The debug output, up to the crash-point is:
>debug1: identity file authorized_keys2 type 2
>debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p1
>debug1: match: OpenSSH_3.7.1p1 pat OpenSSH*
>debug1: Enabling compatibility mode for protocol 2.0
>           16  [main] ssh 685 handle_exceptions: Exception:
>STATUS_ACCESS_VIOLATION


<snip>


>If anyone can shed any light on this, I'd be chuffed.
>


Did you try the latest version of OpenSSH and Cygwin? 




--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (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/