Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List 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 , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: ssh.exe 3.7.1p1: crashing with STATUS_ACCESS_VIOLATION error @ 0x016E65A8 In-Reply-To: References: 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 >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/