X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: carolus Subject: Re: ssh public key authentication problem using curl Date: Thu, 03 Nov 2011 19:40:04 -0500 Lines: 11 Message-ID: References: <1320361719 DOT 8276 DOT 11 DOT camel AT YAAKOV04> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 11/3/2011 6:57 PM, carolus wrote: I tried > appending the public DSA key from the client to known_hosts on the > server, but that didn't change anything. Correction: What I did was to append id_dsa.pub from the client to authorized_keys on the server, and to delete known_hosts on the server in case there was a conflict with prior data. There was no change in the behavior of either "ssh -v host" or "curl -v -O sftp://host/path". -- 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