This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ssh.exe 3.7.1p1: crashing with STATUS_ACCESS_VIOLATION error @ 0x016E65A8
- From: Larry Hall <lh-no-personal-replies-please at cygwin dot com>
- To: Wayne A McAuliffe <waynemc at au1 dot ibm dot com>, cygwin at cygwin dot com
- Date: Tue, 19 Oct 2004 09:01:32 -0400
- Subject: Re: ssh.exe 3.7.1p1: crashing with STATUS_ACCESS_VIOLATION error @ 0x016E65A8
- References: <loom.20041019T012057-477@post.gmane.org>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
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/