f3c11692a9
Daniel Stenberg
2026-06-29
Subject
CURLOPT_SSH_*_KEYFILE: used for setting up, then no more
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/libcurl/opts/CURLOPT_SSH_PRIVATE_KEYFILE.md +6 -2docs/libcurl/opts/CURLOPT_SSH_PUBLIC_KEYFILE.md +5 -0
docs/libcurl/opts/CURLOPT_SSH_PRIVATE_KEYFILE.md+6 -2
| @@ -33,8 +33,7 @@ used, libcurl defaults to **$HOME/.ssh/id_rsa** or **$HOME/.ssh/id_dsa** if | |
| the HOME environment variable is set, and in the current directory if HOME is | |
| not set. | |
| - | If the file is password-protected, set the password with |
| - | CURLOPT_KEYPASSWD(3). |
| + | If the file is password-protected, set the password with CURLOPT_KEYPASSWD(3). |
| The SSH library derives the public key from this private key when possible. If | |
| the SSH library cannot derive the public key from the private one and no | |
| @@ -44,6 +43,11 @@ fails. | |
| The application does not have to keep the string around after setting this | |
| option. | |
| + | This option is used to set up a new connection only. The private key is used |
| + | when libcurl establishes a new SSH connection; once that connection has been |
| + | successfully set up and verified, it is deemed vetted and may be reused by |
| + | libcurl even if this option is changed. |
| + | |
| # DEFAULT | |
| As explained above | |
docs/libcurl/opts/CURLOPT_SSH_PUBLIC_KEYFILE.md+5 -0
| @@ -40,6 +40,11 @@ no public one is provided, the transfer fails. | |
| The application does not have to keep the string around after setting this | |
| option. | |
| + | This option is used to set up a new connection only. The public key is used |
| + | when libcurl establishes a new SSH connection; once that connection has been |
| + | successfully set up and verified, it is deemed vetted and may be reused by |
| + | libcurl even if this option is changed. |
| + | |
| # DEFAULT | |
| NULL | |