X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=2.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED X-Spam-Check-By: sourceware.org Date: Fri, 6 Apr 2012 02:44:49 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <612505306.20120406024449@mtu-net.ru> To: Rurik Christiansen , cygwin@cygwin.com Subject: Re: sshd not doing key based authentication In-Reply-To: <4F7D2BBA.1080004@gmail.com> References: <4F7C0884.2080006@gmail.com> <74924010.20120404152639@mtu-net.ru> <20120404133001.GA8876@pris.crapsteak.org> <4F7D2BBA.1080004@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 Greetings, Rurik Christiansen! > The "ssh -vvv' (client side) has not been particularly helpful to me > when it comes to permissions. That's because server will not disclose any potential vulnerabilities to client. > and my understanding is that I can't run the sshd frontend without > screwing the permissions. I don't understand what you mean by this. > (the client sends the publickey packet and then jumps to next auth method) This looks exactly like wrong permissions on authorized_keys file, or absence of it for particular user. Also, please don't top-post. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 06.04.2012, <02:42> Sorry for my terrible english... -- 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