From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: openssh: privilege separation no longer supported on Cygwin? SURPRISE!
Date: Wed, 31 May 2017 19:52:00 -0000 [thread overview]
Message-ID: <3379afa6b42f91b1cc23cada04ce40b6@smtp-cloud3.xs4all.net> (raw)
In-Reply-To: <b4649f29-b2bb-b735-463b-91cbe7e13654@gmail.com>
On Wed, 31 May 2017 10:59:38, cyg Simple wrote:
> On 5/31/2017 10:16 AM, Houder wrote:
> > On Wed, 31 May 2017 09:27:02, cyg Simple wrote:
> >
> > [snip]
> >> All of this talk of /etc/passwd leads me to point you to
> >> https://cygwin.com/cygwin-ug-net/ntsec.html.
> >
> > cyg,
> >
> > Do you want me to study that text a second, third, fourth or Xth time ...?
> >
>
> Yes, especially section
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping where it
> explains that /etc/passwd and /etc/group are now deprecated and it's use
> is for backward compatibility and that you should be using
> /etc/nsswitch.conf[1] instead. Have you attempted this?
>
> [1] https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch
Actually, that text reads:
= Mapping Windows SIDs to POSIX uid/gid values:
* Read /etc/passwd and /etc/group files if they exist, just as in the olden
days, mainly for backward compatibility.
-----
It does not stipulate that these files are no longer supported ... Corinna did
not dare to proclaim them "deprecated".
Do I use the file /etc/nsswitch.conf? Yes, certainly. As shown in:
https://cygwin.com/ml/cygwin/2017-05/msg00456.html
(see bottom of post)
Do you want me to drop /etc/{passwd,group} files. Yes, you do. I will not.
Moreover, it is completely irrelevant from a logical point of view whether
/etc/{passwd,group) or AD is used to maintain the "network administration".
Regards,
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-05-31 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 6:40 openssh: privilege separation no longer supported on Cygwin? Houder
2017-05-29 9:22 ` Marco Atzeri
2017-05-29 11:39 ` Houder
2017-05-29 11:44 ` openssh: privilege separation no longer supported on Cygwin? -- example only Houder
2017-05-29 14:29 ` openssh: privilege separation no longer supported on Cygwin? Houder
2017-05-29 17:45 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! Houder
2017-05-29 20:30 ` Andrey Repin
2017-05-30 3:49 ` Houder
2017-05-30 16:16 ` Houder
2017-05-31 4:58 ` Larry Hall (Cygwin)
2017-05-31 10:51 ` Houder
2017-05-31 14:46 ` cyg Simple
2017-05-31 14:57 ` Houder
2017-05-31 14:59 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! -- minor correction Houder
2017-05-31 16:34 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! cyg Simple
2017-05-31 19:52 ` Houder [this message]
2017-05-31 20:16 ` cyg Simple
2017-06-01 2:27 ` Larry Hall (Cygwin)
2017-05-31 20:20 ` openssh: privilege separation no longer supported on Cygwin? Marco Atzeri
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=3379afa6b42f91b1cc23cada04ce40b6@smtp-cloud3.xs4all.net \
--to=houder@xs4all.nl \
--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).