From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Simplify AD integration?
Date: Wed, 30 Jul 2014 17:11:00 -0000 [thread overview]
Message-ID: <53D9270B.3010007@cygwin.com> (raw)
In-Reply-To: <20140730134716.GM25860@calimero.vinschen.de>
On 07/30/2014 09:47 AM, Corinna Vinschen wrote:
> Hi folks,
>
>
> here's a set of question to those of you interested in the new
> passwd/group functionality. This already has been discussed partially,
> but there was no conclusion.
>
> Right now, there's a lot of variability in the user names, based on the
> /etc/nsswitch.conf settings db_prefix and db_separator.
>
> The separator char is a '+' by default but can be replaced with other
> ASCII chars. db_prefix allows three styles of user naming conventions:
>
> Default is 'auto':
>
> builtin accounts; "+SYSTEM", "+LOCAL", etc.
> primary domain "corinna", "cgf", ...
> other domain: "DOMAIN1+walter", "DOMAIN2+mathilda"
>
> If set to 'primary':
>
> builtin accounts; "+SYSTEM", "+LOCAL", etc.
> primary domain "MYDOMAIN+corinna", "MYDOMAIN+cgf", ...
> other domain: "DOMAIN1+walter", "DOMAIN2+mathilda"
>
> If set to 'always':
>
> builtin accounts; "NT AUTHORITY+SYSTEM", "BULTIN+LOCAL", etc.
> primary domain "MYDOMAIN+corinna", "MYDOMAIN+cgf", ...
> other domain: "DOMAIN1+walter", "DOMAIN2+mathilda"
>
> "Primary domain" here is either the primary domain of the machine or the
> local SAM if the machine is no domain member. "Other domain" here is
> either a trusted domain or the local SAM for domain machines.
>
> Together with the variable separator char this is an awful lot of
> variability, which has the potential side effect to complicate the
> code *and* debugging.
>
> Also, the leading '+' for builtin accounts results in some downsides,
> one of them for instance the fact that `chown +x' assumes that x is a
> numerical uid or gid. Thus `chown +SYSTEM ...' fails. On the other
> hand it simplifies the account handling inside of Cygwin.
>
> So I'd like to ask a few questions to which I'd like to have some brief
> answers, kind of like a poll, to get a better idea how we should
> proceed:
>
> 1. Shall we remove the leading '+' from the builtin account names
> or shall we keep it?
I'd say remove it since it isn't providing a clear benefit and,
more importantly, causes regressions in some cases with existing tools
(as you stated above with chown).
> 2. Shall we stick to '+' as the separator char or choose another one?
> If so, which one?
Did the discussion of this before end up inconclusive? I thought that
'+' was seen as preferable for some reason that received some overall
approval.
> 3. Shall we keep the `db_prefix' variability or choose one of
> the prefixing methods and stick to it? If so, which one, auto,
> primary, or always?
My opinion is that options are only necessary when there's no clear
single solution. If it's very clear that there is no way to merge
all these possibilities into 1 or one is not clearly a superset of
the others, then we need to keep the options. We shouldn't keep the
options just to have options obviously. :-)
> Bonus question:
>
> 4. Should Cygwin downcase all usernames when generating the Cygwin
> username, so, if your Windows username is 'Ralph', your Cygwin
> username will be 'ralph'?
This is enticing since it's a more common convention for UNIX/Linux
environments, which Cygwin strives to mimic. But I would say that
downcasing isn't desirable since it just upholds a convention. The
convention isn't a requirement so it shouldn't be enforced.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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:[~2014-07-30 17:11 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:47 Corinna Vinschen
2014-07-30 14:38 ` Achim Gratz
2014-07-30 15:01 ` Corinna Vinschen
2014-07-30 16:33 ` Achim Gratz
2014-07-30 22:05 ` Andrey Repin
2014-07-30 15:29 ` Wolf Geldmacher
2014-07-30 15:43 ` Corinna Vinschen
2014-07-30 17:00 ` Eric Blake
2014-07-30 18:10 ` Eric Blake
2014-07-30 17:11 ` Larry Hall (Cygwin) [this message]
2014-07-30 17:28 ` Eric Blake
2014-07-30 18:10 ` Eric Blake
2014-07-30 18:43 ` Corinna Vinschen
2014-07-31 7:13 ` Achim Gratz
2014-08-01 9:23 ` Corinna Vinschen
2014-08-01 17:43 ` Achim Gratz
2014-08-01 18:22 ` Corinna Vinschen
2014-08-01 18:25 ` Achim Gratz
2014-08-01 18:43 ` Corinna Vinschen
2014-08-04 19:00 ` Corinna Vinschen
2014-08-06 8:48 ` Corinna Vinschen
2014-09-01 11:42 ` Corinna Vinschen
2014-07-30 19:37 ` Achim Gratz
2014-07-30 18:15 ` Andrew DeFaria
2014-07-30 18:40 ` Corinna Vinschen
2014-07-30 18:44 ` Corinna Vinschen
2014-07-30 19:09 ` Eric Blake
2014-07-30 19:23 ` Stephan Mueller
2014-07-30 19:32 ` Corinna Vinschen
2014-07-30 19:29 ` Corinna Vinschen
2014-07-30 19:43 ` Corinna Vinschen
2014-07-30 20:04 ` Andrew DeFaria
2014-07-30 20:49 ` Larry Hall (Cygwin)
2014-07-30 21:19 ` Andrew DeFaria
2014-07-30 22:20 ` Andrey Repin
2014-07-30 22:24 ` Larry Hall (Cygwin)
2014-08-01 9:25 ` Corinna Vinschen
2014-08-01 17:44 ` Achim Gratz
2014-08-01 18:12 ` Corinna Vinschen
2014-08-01 18:22 ` Achim Gratz
2014-08-01 18:50 ` Corinna Vinschen
2014-08-01 19:06 ` Achim Gratz
2014-07-31 13:22 ` D. Boland
2014-07-31 14:17 ` Eric Blake
2014-07-31 15:35 ` D. Boland
2014-07-31 22:20 ` Andrey Repin
2014-08-01 12:24 ` D. Boland
2014-08-01 17:16 ` Andrew DeFaria
2014-08-01 18:13 ` Corinna Vinschen
2014-08-01 9:31 ` Corinna Vinschen
2014-07-31 21:06 ` AW: " Christoph H. Hochstaetter
2014-08-01 10:01 ` Corinna Vinschen
2014-08-01 15:18 ` Larry Hall (Cygwin)
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=53D9270B.3010007@cygwin.com \
--to=reply-to-list-only-lh@cygwin.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).