From: Dave Pinsker <davep@pinsker.cncdsl.com>
To: cygwin@cygwin.com
Subject: Re: Illegal User Error Attempting to Authenticate in sshd
Date: Wed, 05 Dec 2001 12:06:00 -0000 [thread overview]
Message-ID: <200112052003.PAA06299@arkroyal.cnchost.com> (raw)
In-Reply-To:
Thanks for your quick response, Corinna.
> A good way to debug problems in sshd when started as service is,
> Use `-d' instead of `-D' as argument.
I am using sshd's '-d' switch to dump the output quoted in my last
message (please see last thread).
> Another very important point is, check the permissions of the
> /etc directory and the permissions of /etc/passwd, /etc/group
> and /etc/ssh* overcarefully. After an installation with setup,
> the permissions are sometimes so that SYSTEM doesn't have
> appropriate permissions on /etc or subsequent files as soon as
> `ntsec' is used. It's not necessary for SYSTEM to have write
> access but read access should be given. So try
>
> chmod 755 /etc
> chmod 644 /etc/passwd /etc/group
These perms are already correct, but attempting to chmod anything
does not modify permissions. The command does not produce an error
(and $? is 0), but no changes are made on the files. chown also
fails in the same manner. All files are owned by whomever is logged
in at the time (tried: Dave Pinsker and SYSTEM).
I had attributed this to the fact that I'm running FAT32, vs. NTFS,
and hence, do not have the extended set of permissions available --
logical? I realize most implementations are probably on NTFS, but
should there be any issues running on FAT32?
Thanks,
_Dave_
davep@interaccess.com
--
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/
next reply other threads:[~2001-12-05 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 12:06 Dave Pinsker [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-18 13:34 Dave Pinsker
2001-12-20 10:06 ` Dave Pinsker
2001-12-20 10:42 ` Dave Pinsker
2001-12-04 15:56 Dave Pinsker
2001-12-05 0:47 ` Corinna Vinschen
2001-12-05 1:32 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200112052003.PAA06299@arkroyal.cnchost.com \
--to=davep@pinsker.cncdsl.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).