public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Simplify AD integration?
Date: Fri, 01 Aug 2014 10:01:00 -0000	[thread overview]
Message-ID: <20140801100149.GC25860@calimero.vinschen.de> (raw)
In-Reply-To: <259120036f9fe92106ee2f4344c83734@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]

On Jul 31 23:06, Christoph H. Hochstaetter wrote:
> Corinna Vinschen wrote:
> >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"
> 
> >1. Shall we remove the leading '+' from the builtin account names
> >   or shall we keep it?
> 
> None of these three seem correct to me. It should be:
> 
> builtin accounts;   "NT AUTHORITY+SYSTEM", "BULTIN+LOCAL", etc.
> primary domain      "corinna", "cgf", ...
> other domain:       "DOMAIN1+walter", "DOMAIN2+mathilda"

The prefix-only variation for builtin and well-known acocunts is what's
originally used by SFU.  I cloned that behaviour as it seemed to have
advantages handling getpwname/getgrnam calls.

> Windows treats "NT AUTHORITY" and "BUILTIN" as foreign domains like DOMAIN1
> and DOMAIN2 in Win32 APIs that use a single string for domain and username,
> e.g. lpServiceStartName in CreateService. Examples:
> 
> ".\user1" - can be uses as a shortcut for "MYDOMAIN\user1"
> [...]

The Windows ".\" prefixing is not at all utilized inside Cygwin.  It has
nothing to do with how the prefixing is evaluated.

> This should be at least configurable thru
> db_prefix even though most users might not want to see names like " NT
> AUTHORITY+SYSTEM " in ls -l.

That's what you get with db_prefix "auto" or "primary".

> >2. Shall we stick to '+' as the separator char or choose another one?
> >   If so, which one?
> 
> Yes "+" is well known for that purpose in Linux and other Unixes. Keep
> db_separator in /etc/nsswitch.conf if possible
> 
> >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?
> See above
> 
> >Bonus question:
> >
> >4. Should Cygwin downcase all usernames when generating the Cygwin
> >   username
> I prefer downcase. Other users probably will not. So db_username_downcase =
> true/false would be great.

Sigh.  YA setting.  I was trying to *simplify* the stuff and reduce
variability since that stuff only complicates the code for... what
gain?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-01 10:01 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)
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 [this message]
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=20140801100149.GC25860@calimero.vinschen.de \
    --to=corinna-cygwin@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).