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: Wed, 30 Jul 2014 15:01:00 -0000	[thread overview]
Message-ID: <20140730150100.GO25860@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20140730T161203-159@post.gmane.org>

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

On Jul 30 14:38, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > 1. Shall we remove the leading '+' from the builtin account names
> >    or shall we keep it?
> 
> I'd rather keep it since it's a good reminder where that comes from.
>  
> > 2. Shall we stick to '+' as the separator char or choose another one?
> >    If so, which one?
> 
> WJFFM at the moment, so I don't see a pressing need for variability.
> 
> > 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?
> 
> I'd rather keep this, although "auto" is all I use at the moment.  BTW,
> would it be possible to recognize PRIMARYDOMAIN+user and (auto) user be
> recognized as the same thing when auto is in effect?  The ability to
> explicitly specify the prefix even though it isn't necessarily displayed
> would most likely remove much of the potential need for variability in that
> department

I'm not sure if that would work as expected. Cygwin explicitely tests
if the account name follows the current rule.  I'm not so sure what
effects it would have, if getpwnam could return another username as
the one given as parameter (apart from the case difference).

(and defuse the booby trap in chown).

Well, hmm.  If we allow to specify "NT AUTHORITY+SYSTEM" or
"BUILTIN+Administrators" even in "auto" or "primary" mode...

Unfortunately this won't help in all cases.  I used a broken example :(
The "LOCAL" account and a few others have NO domain.  Thus, they are
simply +-prefixed ("+LOCAL"), even in 'db_prefix: always' mode.

Tricky.

> If you keep it, then there's an obvious candidate missing: "local+other",
> which should prefix all accounts except the primary domain ones.

Do you mean

  builtin accounts;   "NT AUTHORITY+SYSTEM", "BUILTIN+Administrators", ...
  primary domain      "corinna", "cgf", ...
  other domain:       "DOMAIN1+walter", "DOMAIN2+mathilda"

?

> So it'd be
> better to simply flag which groups to prefix, I'd think ("local", "primary",
> "other") and specify this like symbolic modes in chmod, perhaps?
> 
> > 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'?
> 
> I'd be in favor of this since I've already had two users that wouldn't see
> their home directories until I figured out that they'd have their names
> capitalized in AD...  as long as Windows is unable to distinguish users
> based on the case there shouldn't be a problem.


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-07-30 15: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 [this message]
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
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=20140730150100.GO25860@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).