X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 9 Sep 2008 14:48:40 -0600 From: Tom Schutter To: cygwin AT cygwin DOT com Subject: Re: SSH publickey problem, password works (Win 2003, OpenSSH_5.1p1, Cygwin DLL1.5.25 ) Message-ID: <20080909204840.GF12841@proxix.com> References: <48C640CF DOT 6060809 AT scn DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48C640CF.6060809@scn.org> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) 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 Tue 08-09-09 04:24, Just Me wrote: > I've been fighting with SSH for a week now, I've read everything I can > google, it's finally time to ask for help. > > I can ssh to any account using a password, no problem. It bombs with a > cannot seteuid error in the event log when I use a keypair. I just solved this yesterday on my box. If you get a "Connection closed by xxx.xxx.xxx.xxx" message when using ssh to connect to a Cygwin sshd server, and/or the event log on the server machine contains the error "sshd: PID XXXX: fatal: seteuid YYYYY: Permission denied", the user account that sshd is running under probably does not have the "Create a token object" right. Note that if the account does not have this right, it probably doen't have other important rights as well. These rights are normally setup by the ssh-host-config script for the sshd_server user. -- Tom Schutter First American - Proxix Solutions 303-440-7272 x6822 -- 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/