Re: Curl Library asking for key authentication when it shouldn't?
Date: Thu, 17 Feb 2011 17:34:20 -0500
Additionally, the directory /home/sali/.ssh/ only contains one file:
known_hosts. Each line in this file contains what looks like an RSA key (the
string directly after the IP address == "ssh-rsa")
So how can I tell libcurl to use RSA keys instead of DSA keys? And shouldn't
the keys be irrelevant if I'm providing a username/password?
On Thu, Feb 17, 2011 at 4:45 PM, Saqib Ali <saqib.ali.75_at_gmail.com> wrote:
> I'm using the recipe described here to do an SCP using the Curl Library
> (version 7.21.3)
> I'm simply trying to send the file to the same host+username as myself. IE:
> Here is the output I get:
> * About to connect() to 127.0.0.1 port 22 (#0)
> * Trying 127.0.0.1... * connected
> * Connected to 127.0.0.1 (127.0.0.1) port 22 (#0)
> * SSH authentication methods available:
> * Using ssh public key file /home/sali/.ssh/id_dsa.pub
> * Using ssh private key file /home/sali/.ssh/id_dsa
> * SSH public key authentication failed: Unable to open public key file
> * Initialized password authentication
> * Authentication complete
> * Upload failed: Permission denied (3/-31)
> * Connection #0 to host 127.0.0.1 left intact
> * Access denied to remote resource
> Why is it complaining about public/private keys when I'm providing a
> password? Other people seem to be using it without that problem.
> Do I need to set some other curl options to tell it to do this transfer
> without any keys?
> BTW, I know little about key authentication. If you're response includes
> discussion about them, please speak VERRY SLOOOWWWLLLY.
> - Saqib
List admin: http://cool.haxx.se/list/listinfo/curl-library
Received on 2011-02-17