This is the mail archive of the
mailing list for the Cygwin project.
Re: Administrator lacking super-user privileges on cygwin installation
- From: Myk Melez <myk at aol dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 01 Aug 2003 11:35:34 -0700
- Subject: Re: Administrator lacking super-user privileges on cygwin installation
- References: <3F299C67.email@example.com> <3F29C4F1.firstname.lastname@example.org>
Larry Hall wrote:
1. SYSTEM is the account that sshd runs as, not administrator.
Hmm, perhaps it's just a coincidence then that Administrator permissions
correspond with sshd permissions.
2. Only the owner of the private key files in .ssh should have
to access these files. Public key files should be readable by anyone.
You'll want to check the permissions on these files relative to the
We got things working by opening up public access to
/home/some-user/.ssh/authorized_keys, and perhaps that's sufficient,
although I'm still concerned about the difference in behavior across my
two installations. I have limited experience with cygwin (or Windows in
general), but on Linux in my experience sshd turns up its nose at
non-private .ssh directories, or else I would have tried that sooner.
$CYGWIN is set to "binmode ntsec tty", so that shouldn't be the problem.
3. Generally, you should read <http://cygwin.com/problems.html>.
I've been through the FAQ and User's Guide but couldn't find an answer
to my question. Perhaps I should read both straight through for a more
rounded understanding of what's going on; I was just hoping someone had
experienced this before and knew the magic incantation to correct it. :-)
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html