ssh: make CURLOPT_SSH_PUBLIC_KEYFILE treat "" as NULL
The CURLOPT_SSH_PUBLIC_KEYFILE option has been documented to handle empty strings specially since curl-7_25_0-31-g05a443a but the behavior was unintentionally removed in curl-7_38_0-47-gfa7d04f. This commit restores the original behavior and clarifies it in the documentation that NULL and "" have both the same meaning when passed to CURLOPT_SSH_PUBLIC_KEYFILE. Bug: http://curl.haxx.se/mail/lib-2016-01/0072.html
This commit is contained in:
@@ -35,11 +35,11 @@ libcurl defaults to \fB$HOME/.ssh/id_dsa.pub\fP if the HOME environment
|
||||
variable is set, and just "id_dsa.pub" in the current directory if HOME is not
|
||||
set.
|
||||
|
||||
If an empty string is passed, libcurl will pass no public key to libssh2 which
|
||||
then tries to compute it from the private key, this is known to work when
|
||||
libssh2 1.4.0+ is linked against OpenSSL.
|
||||
If NULL (or an empty string) is passed, libcurl will pass no public key to
|
||||
libssh2, which then tries to compute it from the private key. This is known
|
||||
to work with libssh2 1.4.0+ linked against OpenSSL.
|
||||
.SH DEFAULT
|
||||
As explained above
|
||||
NULL
|
||||
.SH PROTOCOLS
|
||||
SFTP and SCP
|
||||
.SH EXAMPLE
|
||||
|
Reference in New Issue
Block a user