Tests 3021 and 3022 (SSH SHA256 host keys) fail if curl is built with libssh rather than libssh2 · Issue #8009 · curl/curl · GitHub
Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Tests 3021 and 3022 (SSH SHA256 host keys) fail if curl is built with libssh rather than libssh2 #8009 New issue Copy link New issue Copy link Closed Closed Tests 3021 and 3022 (SSH SHA256 host keys) fail if curl is built with libssh rather than libssh2 #8009 Copy link Assignees Labels SCP/SFTP tests Description pghmcfc opened on Nov 13, 2021 Issue body actions I did this Built curl with libssh as the SSH back-end.
Ran the test suite. ... test 3021...[SFTP correct sha256 host key] ../src/curl --output log/curl3021.out --include --trace-ascii log/trace3021 --trace-time --hostpubsha256 tuofrme8Oa2zL+lDozIdDoMsAap/7J9rRPHlf0A/nU4 --key curl_client_key --pubkey curl_client_key.pub -u mockbuild: sftp://127.0.0.1:20025/builddir/build/BUILD/curl-7.80.0/build-full/tests/log/file3021.txt >log/stdout3021 2>log/stderr3021 CMD (15360): ../src/curl --output log/curl3021.out --include --trace-ascii log/trace3021 --trace-time --hostpubsha256 tuofrme8Oa2zL+lDozIdDoMsAap/7J9rRPHlf0A/nU4 --key curl_client_key --pubkey curl_client_key.pub -u mockbuild: sftp://127.0.0.1:20025/builddir/build/BUILD/curl-7.80.0/build-full/tests/log/file3021.txt >log/stdout3021 2>log/stderr3021 3021: data FAILED: --- log/check-expected 2021-11-10 21:37:39.283719015 +0000 +++ log/check-generated 2021-11-10 21:37:39.282718930 +0000 @@ -1 +0,0 @@ -test[LF] == Contents of files in the log/ dir after test 3021 === Start of file check-expected test[LF] === End of file check-expected === Start of file commands.log ../src/curl --output log/curl3021.out --include --trace-ascii log/trace3021 --trace-time --hostpubsha256 tuofrme8Oa2zL+lDozIdDoMsAap/7J9rRPHlf0A/nU4 --key curl_client_key --pubkey curl_client_key.pub -u mockbuild: sftp://127.0.0.1:20025/builddir/build/BUILD/curl-7.80.0/build-full/tests/log/file3021.txt >log/stdout3021 2>log/stderr3021 === End of file commands.log === Start of file file3021.txt test === End of file file3021.txt === Start of file ftpserver.cmd Testnum 3021 === End of file ftpserver.cmd === Start of file stderr3021 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (60) SSL peer certificate or SSH remote key was not OK More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it.
To learn more about this situation and how to fix it, please visit the web page mentioned above. === End of file stderr3021 === Start of file trace3021 21:37:39.478502 == Info: Trying 127.0.0.1:20025... 21:37:39.480092 == Info: Connected to 127.0.0.1 (127.0.0.1) port 20025 (#0) 21:37:39.480793 == Info: User: mockbuild 21:37:39.480803 == Info: Known hosts: /builddir/build/BUILD/curl-7.80.0/build-full/tests/.ssh/known_hosts 21:37:39.680504 == Info: Closing connection 0 === End of file trace3021 test 3022...[SCP correct sha256 host key] ../src/curl --output log/curl3022.out --include --trace-ascii log/trace3022 --trace-time --hostpubsha256 tuofrme8Oa2zL+lDozIdDoMsAap/7J9rRPHlf0A/nU4 --key curl_client_key --pubkey curl_client_key.pub -u mockbuild: scp://127.0.0.1:20025/builddir/build/BUILD/curl-7.80.0/build-full/tests/log/file3022.txt >log/stdout3022 2>log/stderr3022 CMD (15360): ../src/curl --output log/curl3022.out --include --trace-ascii log/trace3022 --trace-time --hostpubsha256 tuofrme8Oa2zL+lDozIdDoMsAap/7J9rRPHlf0A/nU4 --key curl_client_key --pubkey curl_client_key.pub -u mockbuild: scp://127.0.0.1:20025/builddir/build/BUILD/curl-7.80.0/build-full/tests/log/file3022.txt >log/stdout3022 2>log/stderr3022 3022: data FAILED: --- log/check-expected 2021-11-10 21:37:39.521739376 +0000 +++ log/check-generated 2021-11-10 21:37:39.521739376 +0000 @@ -1 +0,0 @@ -test[LF] == Contents of files in the log/ dir after test 3022 === Start of file check-expected test[LF] === End of file check-expected === Start of file commands.log ../src/curl --output log/curl3022.out --include --trace-ascii log/trace3022 --trace-time --hostpubsha256 tuofrme8Oa2zL+lDozIdDoMsAap/7J9rRPHlf0A/nU4 --key curl_client_key --pubkey curl_client_key.pub -u mockbuild: scp://127.0.0.1:20025/builddir/build/BUILD/curl-7.80.0/build-full/tests/log/file3022.txt >log/stdout3022 2>log/stderr3022 === End of file commands.log === Start of file file3022.txt test === End of file file3022.txt === Start of file ftpserver.cmd Testnum 3022 === End of file ftpserver.cmd === Start of file stderr3022 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (60) SSL peer certificate or SSH remote key was not OK More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it.
To learn more about this situation and how to fix it, please visit the web page mentioned above. === End of file stderr3022 === Start of file trace3022 21:37:39.718869 == Info: Trying 127.0.0.1:20025... 21:37:39.719721 == Info: Connected to 127.0.0.1 (127.0.0.1) port 20025 (#0) 21:37:39.720082 == Info: User: mockbuild 21:37:39.720088 == Info: Known hosts: /builddir/build/BUILD/curl-7.80.0/build-full/tests/.ssh/known_hosts 21:37:39.919123 == Info: Closing connection 0 === End of file trace3022 setenv CURL_SSL_BACKEND = schannel setenv CURL_SSL_BACKEND = schannel * kill pid for ftp-ctrl => 1771933 * kill pid for ftp-ipv6-ctrl => 1773967 * kill pid for imap-filt => 1783039 * kill pid for pop3-filt => 1786297 * kill pid for smtp-filt => 1782981 * kill pid for ftp-ipv6 => 1773966 * kill pid for http => 1805768 * kill pid for https => 1805784 * kill pid for https => 1805788 * kill pid for socks => 1780532 * kill pid for dict => 1802015 * kill pid for telnet => 1802082 * kill pid for gopher => 1795963 * kill pid for tftp => 1797157 * kill pid for smtp => 1782980 * kill pid for ftp => 1771932 * kill pid for mqtt => 1795613 * kill pid for http/2 => 1804750 * kill pid for http/2 => 1804752 * kill pid for http-ipv6 => 1773584 * kill pid for https-proxy => 1804565 * kill pid for https-proxy => 1804569 * kill pid for gopher-ipv6 => 1796072 * kill pid for smb => 1802047 * kill pid for http-unix => 1801539 * kill pid for httptls => 1776268 * kill pid for rtsp => 1780626 * kill pid for http-proxy => 1768561 * kill pid for pop3 => 1786296 * kill pid for imap => 1783038 * kill pid for ssh => 1781167 * kill pid for ssh => 1781097 * kill pid for ftps => 1777948 * kill pid for ftps => 1777952 RUN: Process with pid 1768561 signalled to die RUN: Process with pid 1771932 signalled to die RUN: Process with pid 1773584 signalled to die RUN: Process with pid 1773966 signalled to die RUN: Process with pid 1776268 signalled to die RUN: Process with pid 1777948 signalled to die RUN: Process with pid 1777952 signalled to die RUN: Process with pid 1780532 signalled to die RUN: Process with pid 1780626 signalled to die RUN: Process with pid 1781097 signalled to die RUN: Process with pid 1781167 signalled to die RUN: Process with pid 1782980 signalled to die RUN: Process with pid 1783038 signalled to die RUN: Process with pid 1786296 signalled to die RUN: Process with pid 1795613 signalled to die RUN: Process with pid 1795963 signalled to die RUN: Process with pid 1796072 signalled to die RUN: Process with pid 1797157 signalled to die RUN: Process with pid 1801539 signalled to die RUN: Process with pid 1802015 signalled to die RUN: Process with pid 1802047 signalled to die RUN: Process with pid 1802
The rest of this page is on the live site.