Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Marc Poppleton" To: Subject: RE: SSH key authentification problem Date: Mon, 19 Jan 2004 11:19:23 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes Whops! chmod 777 to reverse then! :) I omited to say that I have absolutely no control on the Linux side (and, just to make it easier, the admin is out for the day). Looking at the debug log, I guess that this: debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Trying private key: /cygdrive/c/.ssh/identity debug1: Trying private key: /cygdrive/c/.ssh/id_rsa debug1: Offering public key: /cygdrive/c/.ssh/id_dsa debug1: Authentications that can continue: publickey,password debug1: Next authentication method: password mylogin AT theserver's password: means something like: trying with publickey but finaly trying with password. Question is : why? Is something going wrong with the publickey authentification or is it the normal process to ask for my password after? Marc > -----Message d'origine----- > De : cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]De la part > de jurgen DOT defurne AT philips DOT com > Envoye : lundi 19 janvier 2004 11:05 > Cc : cygwin AT cygwin DOT com > Objet : RE: SSH key authentification problem > > > Marc, > > My suggestion missed the fact that these settings should > be done on the Linux side ! > > Jurgen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/