X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Subject: Re: ssh public key authentication problem using curl From: "Yaakov (Cygwin/X)" To: cygwin Date: Thu, 03 Nov 2011 18:08:38 -0500 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Message-ID: <1320361719.8276.11.camel@YAAKOV04> Mime-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, 2011-11-01 at 15:24 -0500, carolus wrote: > After setup with ssh-host-config, ssh-user-config, and ssh-copy-id, > public key authentication works with ssh but fails with curl. (Password > authentication works with curl -u, but is less convenient.) > > curl -v shows: > > SSH authentication methods available: > publickey,password,keyboard-interactive > Using ssh public key file /home/cdr/.ssh/id_dsa.pub > Using ssh private key file /home/cdr/.ssh/id_dsa > SSH public key authentication failed: Username/PublicKey combination > invalid > Authentication failure > > However, ssh authenticates OK using RSA. ssh -v shows: > > Next authentication method: publickey > Offering public key: /home/cdr/.ssh/id_rsa > Server accepts key: pkalg ssh-rsa blen 279 > read PEM private key done: type RSA > Authentication succeeded (publickey). Look at the output: You're using the wrong keys with the curl command. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple