public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: curl SFTP transfer from Cygwin on Win10 to Ubuntu 18.04 fails with Unknown host key type: 1835008
Date: Fri, 14 May 2021 23:47:15 -0600	[thread overview]
Message-ID: <97187a2e-3310-28fc-157f-65e795262382@SystematicSw.ab.ca> (raw)
In-Reply-To: <CS1PR8401MB0661782A5CCF9842B233F87CFE509@CS1PR8401MB0661.NAMPRD84.PROD.OUTLOOK.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@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.]

  reply	other threads:[~2021-05-15  5:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  4:40 Voris, Ben
2021-05-15  5:47 ` Brian Inglis [this message]
2021-05-17 23:55   ` Brian Inglis
     [not found]     ` <4d604b9e-de20-f379-f6cd-902a41d38e43@SystematicSw.ab.ca>
2021-06-03  1:58       ` Voris, Ben
2021-06-03  6:03         ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97187a2e-3310-28fc-157f-65e795262382@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).