Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 26 Oct 2001 10:27:38 -0500 From: Peter Fales To: cygwin AT cygwin DOT com Subject: problems with sshd and RSAAuthentication Message-ID: <20011026102738.B13230@lucent.com> References: <1004109070 DOT 20843 DOT ezmlm AT sources DOT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1004109070.20843.ezmlm@sources.redhat.com>; from cygwin-help@sources.redhat.com on Fri, Oct 26, 2001 at 03:11:10PM -0000 I'm currently trying to get sshd access to our Cygwin/Win2000 machine. Currently it works well using password authentication, but I can't get it to use RSAAuthentication - it seems to be accepting the key, but then exits right away and creates a windows event log entry: 10/26/2001 9:51:38 AM 1 0 0 sshd NT AUTHORITY\SYSTEM EXPNOVE sshd : Win32 Process Id = 0x470 : Cygwin Process Id = 0x470 : fatal: setuid 1000: Not owner I know something like this has been discuseed before, and I've tried to follow all the steps I can find documented: - I've added "CYGWIN=ntsec tty" to the system environement - I've added these rights for the user that is running cygrunsrv and the SYSTEM account: "Act as part of operating system" "Replace a process level token" "Increase quotas" I'm at a loss to understand why this isn't working, particularly since it seems like password authentication would be doing pretty much the same thing. Can anyone suggest what to try next? -- Peter Fales Lucent Technologies, Room 5B-408 N9IYJ 2000 N Naperville Rd PO Box 3033 internet: psfales AT lucent DOT com Naperville, IL 60566-7033 work: (630) 979-8031 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/