CURLOPT_SSH_PUBLIC_KEYFILE(3) curl_easy_setopt options CURLOPT_SSH_PUBLIC_KEYFILE(3)NAME
CURLOPT_SSH_PUBLIC_KEYFILE - set public key file for SSH auth
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSH_PUBLIC_KEYFILE,
char *filename);
DESCRIPTION
Pass a char * pointing to a filename for your public key. If not used, libcurl defaults to $HOME/.ssh/id_dsa.pub if the HOME environment
variable is set, and just "id_dsa.pub" in the current directory if HOME is not set.
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.
The application does not have to keep the string around after setting this option.
DEFAULT
NULL
PROTOCOLS
SFTP and SCP
EXAMPLE
TODO
AVAILABILITY
The "" trick was added in 7.26.0
RETURN VALUE
Returns CURLE_OK if the option is supported, CURLE_UNKNOWN_OPTION if not, or CURLE_OUT_OF_MEMORY if there was insufficient heap space.
SEE ALSO CURLOPT_SSH_PRIVATE_KEYFILE(3), CURLOPT_SSH_AUTH_TYPES(3),
libcurl 7.54.0 December 21, 2016 CURLOPT_SSH_PUBLIC_KEYFILE(3)
Check Out this Related Man Page
CURLOPT_SSH_AUTH_TYPES(3) curl_easy_setopt options CURLOPT_SSH_AUTH_TYPES(3)NAME
CURLOPT_SSH_AUTH_TYPES - set desired auth types for SFTP and SCP
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSH_AUTH_TYPES, long bitmask);
DESCRIPTION
Pass a long set to a bitmask consisting of one or more of CURLSSH_AUTH_PUBLICKEY, CURLSSH_AUTH_PASSWORD, CURLSSH_AUTH_HOST,
CURLSSH_AUTH_KEYBOARD and CURLSSH_AUTH_AGENT.
Set CURLSSH_AUTH_ANY to let libcurl pick a suitable one. Currently CURLSSH_AUTH_HOST has no effect. If CURLSSH_AUTH_AGENT is used, libcurl
attempts to connect to ssh-agent or pageant and let the agent attempt the authentication.
DEFAULT
None
PROTOCOLS
SFTP and SCP
EXAMPLE
TODO
AVAILABILITY
CURLSSH_AUTH_HOST was added in 7.16.1, CURLSSH_AUTH_AGENT was added in 7.28.0
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO CURLOPT_SSH_HOST_PUBLIC_KEY_MD5(3), CURLOPT_SSH_PUBLIC_KEYFILE(3),
libcurl 7.54.0 February 03, 2016 CURLOPT_SSH_AUTH_TYPES(3)
logon to a client unix box as user "evil"
>
>su - hero
enter evil's password
>hero$> ssh-kengen -t dsa
no passphase, id_dsa / id_dsa.pub generated.
>hero$> scp /home/hero/.ssh/id_dsa.pub evil@scp_server:/tmp/id_dsa.pub
now the scp_server,
logon as evil
>su - hero
>hero>mv... (0 Replies)
I couldn't seem to make 'HOME' key work on my remote windows ssh client to a Fedora Core3 server (the home key works perfectly when i'm physically on site.)
To my surprise, using control+V it seems that both my home and insert key send the same escape sequence ^So it must be my windows SSH client... (0 Replies)
Let me put the results of my SSH test:
1) Generated the pub key in my home directory on server1.
2) SCP the pub key to my home directory on server2
3) Tried to send the file from server1 to server via SSH and It was successful
Next:
1) Generated the pub key... (0 Replies)
I wish to generate a id_dsa.pub and id_dsa (Public and Private Key) in a common user group. I have checked the .ssh directory and i have already found id_dsa.pub and id_dsa existing.
Is that OK if i create both the keys in my home direcotry, rename it to jjj.pub and jjj and move to Common user... (1 Reply)
Hello all
I have question regarding the id_dsa keys and authorized_keys file in .ssh directory.
I know if we try to SFTP, id_dsa.pub file on server1 will be verified with contents of authorized_keys on other server and SFTP will happen once verification passes.
No i want to use id_dsa1.pub... (1 Reply)
Hi,
I need to set up keys between two servers to make a SFTP transfer.
I know the process of generating keys (public and private ) on server1 and moving the public key to server2. But in this case server2 already has a id_dsa.pub file.
Now i may have to add the new key generated on server1... (3 Replies)