Artifactspublic-v0

curl

master
ply4 git calls506 ms288 KiB2 cachedprotocol v2
90 lines2.5 KiBRaw

NAME

CURLOPT_SSH_HOST_PUBLIC_KEY_MD5 - MD5 checksum of SSH server public key

SYNOPSIS

c
#include <curl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSH_HOST_PUBLIC_KEY_MD5,
                          char *md5);

DESCRIPTION

Pass a char pointer pointing to a string containing 32 hexadecimal digits. The string should be the 128-bit MD5 checksum of the remote host's public key, and libcurl aborts the connection to the host unless the MD5 checksum match.

MD5 is a weak algorithm. We strongly recommend using CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256(3) instead.

The application does not have to keep the string around after setting this option.

Using this option multiple times makes the last set string override the previous ones. Set it to NULL to disable its use again.

This option is only applied when libcurl creates a new SSH connection. Once a connection has been created and successfully verified with this MD5 check, it is deemed vetted and may be reused by libcurl without performing the MD5 verification again, even if you later change or disable this option or switch to other verification mechanisms such as CURLOPT_SSH_KNOWNHOSTS(3) or CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256(3). Any such changes only affect future new connections, not already established ones.

When MD5 verification is enabled for a connection via this option, libcurl uses that MD5-based check instead of the known hosts/host key callback verification path for that connection, so you must not assume that both the MD5 check and the known hosts/host key callback verification are performed for the same connection.

DEFAULT

NULL

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  CURL *curl = curl_easy_init();
  if(curl) {
    CURLcode result;
    curl_easy_setopt(curl, CURLOPT_URL, "sftp://example.com/file");
    curl_easy_setopt(curl, CURLOPT_SSH_HOST_PUBLIC_KEY_MD5,
                     "afe17cd62a0f3b61f1ab9cb22ba269a7");
    result = curl_easy_perform(curl);
    curl_easy_cleanup(curl);
  }
}

%AVAILABILITY%

RETURN VALUE

curl_easy_setopt(3) returns a CURLcode indicating success or error.

CURLE_OK (0) means everything was OK, non-zero means an error occurred, see libcurl-errors(3).

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: CURLOPT_SSH_HOST_PUBLIC_KEY_MD5
5Section: 3
6Source: libcurl
7See-also:
8 - CURLOPT_SSH_AUTH_TYPES (3)
9 - CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 (3)
10 - CURLOPT_SSH_KNOWNHOSTS (3)
11 - CURLOPT_SSH_PUBLIC_KEYFILE (3)
12Protocol:
13 - SFTP
14 - SCP
15Added-in: 7.17.1
16---
18# NAME
20CURLOPT_SSH_HOST_PUBLIC_KEY_MD5 - MD5 checksum of SSH server public key
22# SYNOPSIS
24~~~c
25#include <curl/curl.h>
27CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSH_HOST_PUBLIC_KEY_MD5,
28 char *md5);
29~~~
31# DESCRIPTION
33Pass a char pointer pointing to a string containing 32 hexadecimal digits. The
34string should be the 128-bit MD5 checksum of the remote host's public key, and
35libcurl aborts the connection to the host unless the MD5 checksum match.
37MD5 is a weak algorithm. We strongly recommend using
38CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256(3) instead.
40The application does not have to keep the string around after setting this
41option.
43Using this option multiple times makes the last set string override the
44previous ones. Set it to NULL to disable its use again.
46This option is only applied when libcurl creates a new SSH connection. Once a
47connection has been created and successfully verified with this MD5 check, it
48is deemed vetted and may be reused by libcurl without performing the MD5
49verification again, even if you later change or disable this option or switch
50to other verification mechanisms such as CURLOPT_SSH_KNOWNHOSTS(3) or
51CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256(3). Any such changes only affect future new
52connections, not already established ones.
54When MD5 verification is enabled for a connection via this option, libcurl
55uses that MD5-based check instead of the known hosts/host key callback
56verification path for that connection, so you must not assume that both the
57MD5 check and the known hosts/host key callback verification are performed for
58the same connection.
60# DEFAULT
62NULL
64# %PROTOCOLS%
66# EXAMPLE
68~~~c
69int main(void)
71 CURL *curl = curl_easy_init();
72 if(curl) {
73 CURLcode result;
74 curl_easy_setopt(curl, CURLOPT_URL, "sftp://example.com/file");
75 curl_easy_setopt(curl, CURLOPT_SSH_HOST_PUBLIC_KEY_MD5,
76 "afe17cd62a0f3b61f1ab9cb22ba269a7");
77 result = curl_easy_perform(curl);
78 curl_easy_cleanup(curl);
79 }
81~~~
83# %AVAILABILITY%
85# RETURN VALUE
87curl_easy_setopt(3) returns a CURLcode indicating success or error.
89CURLE_OK (0) means everything was OK, non-zero means an error occurred, see
90libcurl-errors(3).
Diagnostics4 git calls · 506 ms
CallStatusSizeTime0506 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.3 KiB501 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=500
git.response.bytes=1331
git.response.cache=MISS
git.response.duration_ms=501
git.fetch.wants=777b25c4a1ba24cb3160443b69ea4ad8cfad1b3e
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1331
git.pkt.payload.max=1310
git.sideband.band1.bytes=1309
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e3a34f9c355751
Request
6d4aaa69…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format