This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin sshd key auth doesn't work (seteuid 500: Permission denied) [SOLVED]
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 19 Nov 2008 12:21:02 -0500
- Subject: Re: Cygwin sshd key auth doesn't work (seteuid 500: Permission denied) [SOLVED]
- References: <4923DCFA.firstname.lastname@example.org> <4923E945.email@example.com>
- Reply-to: cygwin at cygwin dot com
On 11/19/2008, TomÃs NÃÃez wrote:
I've found this doc
and followed the part of "privilege separation". After that, everything
worked fine with key auth.
It's always recommended that you stick with the defaults of the
configuration scripts unless you have a real good reason not to.
Obviously, I'm glad you found the information you needed from any
source though I want to clarify for anyone looking in these archives
in the future that the above site was not material in solving this
problem and any information posted there is not supported by this
list. In short, the solution is, use the defaults of ssh-host-config.
This will set privilege separation, which is what you want.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html