X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C0BC3848407
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=SystematicSw.ab.ca
Authentication-Results: sourceware.org;
 spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis: v=2.4 cv=W+Nb6Tak c=1 sm=1 tr=0 ts=609f6065
 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17
 a=IkcTkHD0fZMA:10 a=kPCIzciLAAAA:20 a=TImcKGuyeGIbufSLrCcA:9 a=QEXdDO2ut3YA:10
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Subject: Re: curl SFTP transfer from Cygwin on Win10 to Ubuntu 18.04 fails
 with Unknown host key type: 1835008
To: cygwin AT cygwin DOT com
References: <CS1PR8401MB0661782A5CCF9842B233F87CFE509 AT CS1PR8401MB0661 DOT NAMPRD84 DOT PROD DOT OUTLOOK DOT COM>
Organization: Systematic Software
Message-ID: <97187a2e-3310-28fc-157f-65e795262382@SystematicSw.ab.ca>
Date: Fri, 14 May 2021 23:47:15 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <CS1PR8401MB0661782A5CCF9842B233F87CFE509@CS1PR8401MB0661.NAMPRD84.PROD.OUTLOOK.COM>
Content-Language: en-CA
X-CMAE-Envelope: MS4xfHkoFKp+7xcdcvxK4RBibgzb/ikwuZllnOoNe4S5NttjAsojgLlSKjHuQyoTXg5/j+hTJpwcMg1qeT82Nw5WLWROgo3VouX4SRx86PjOIZs7w0f96crS
 Z6JmtFSVagiIaQ/riQhF1fZ+7qq28dm15Xmm1p0VA2HD7dm+VIxI+Gsk6V63AGTbjvJaFO4s6zINf47urrv9tjXL9hcTJf/Hek0=
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A,
 RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On 2021-05-13 22:40, Voris, Ben via Cygwin wrote:
> curl issue https://github.com/curl/curl/issues/7057 was closed with:
> "This seems to be purely a libssh2 issue and not a curl one."
> Curl reports "libssh2/1.7.0"
> On the same system, ssh reports " OpenSSH_8.5p1, OpenSSL 1.1.1f  31 Mar 2020"
> The curl code in https://github.com/curl/curl/blob/master/lib/vssh/libssh2.c has a number of defines to control what type of host keys it will accept, including LIBSSH2_KNOWNHOST_KEY_ED25519
> Was the curl built with this set?
> Details are in the curl issue, but here they are again.
> Here is the curl failure:
> : curl -vvv -s -T t.cpp sftp://bvoris AT nucnuc/tmp/t2.cpp
> * STATE: INIT => CONNECT handle 0x800085338; line 1634 (connection #-5000)
> * Added connection 0. The cache now contains 1 members
> * STATE: CONNECT => RESOLVING handle 0x800085338; line 1680 (connection #0)
> * family0 == v4, family1 == v6
> *   Trying 192.168.1.5:22...
> * STATE: RESOLVING => CONNECTING handle 0x800085338; line 1762 (connection #0)
> * Connected to nucnuc (192.168.1.5) port 22 (#0)
> * STATE: CONNECTING => PROTOCONNECT handle 0x800085338; line 1825 (connection #0)
> * SFTP 0x8000847c8 state change from SSH_STOP to SSH_INIT
> * Found host nucnuc in /home/BVoris/.ssh/known_hosts
> * Unknown host key type: 1835008
> * SFTP 0x8000847c8 state change from SSH_INIT to SSH_SESSION_FREE
> * SFTP 0x8000847c8 state change from SSH_SESSION_FREE to SSH_STOP
> * multi_done
> * The cache now contains 0 members
> * SSH DISCONNECT starts now
> * SSH DISCONNECT is done
> * Closing connection 0
> The curl/libcurl version:
> curl 7.76.1 (x86_64-pc-cygwin) libcurl/7.76.1 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.9 zstd/1.4.9 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.0.4) libssh2/1.7.0 nghttp2/1.37.0
> Release-Date: 2021-04-14
> Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
> Features: alt-svc AsynchDNS brotli Debug GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz Metalink NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP TrackMemory UnixSockets zstd
> The known_hosts entry from the client:
> nucnuc ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICmjvQ5jehz5Jwt1PDGJBSgcXVhoMRnbn/E2p3srSK+c
> curl is run on CYGWIN_NT-10.0 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin
> The target system has:
> OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017

Looks like it will need libssh2 1.9.0+.
The next version 1.9.1 is nearing release incorporating all the updated support
as well as all CVE and other patches.

I am working on a couple of build issues, with upstream, and also 32 bit x86 builds.

If I can get those resolved, I could adopt libssh2 (also hosted/supported @haxx.se
involving some of the same folks), releasing an update when the new libssh2 release
is available, and releasing an updated curl release 2 with the updated libssh2.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple