public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
Date: Mon, 14 Apr 2014 23:05:00 -0000	[thread overview]
Message-ID: <205466581.20140415030052@yandex.ru> (raw)
In-Reply-To: <20140414102451.GB24891@calimero.vinschen.de>

Greetings, Corinna Vinschen!

> For clarity: There is no "looking for users first at"...  capability at
> all.  The user is searched via the functions LookupAccountSid and
> LookupAccountName and they decide by themselves in what order to look.

Got it.

>> Environment variable to specify/override default domain on the fly.

> You mean, for deciding which domain goes unprepended?  That would be in
> the nsswitch.conf file, but it would be possible to implement that.
> But does it make sense?  Yet another configuration variable?

Look at it from the usability standpoint. The problem is not the separator
character, the problem is the ambiguity of the account names in certain
situations.
Yes, one of the solutions is to implement a separator character that doesn't
conflict with current functionality, but satisfy the requirement to be a
distinguished separation character.
But this is not the only possible solution.

>> Or even simpler, just an environment variable establishing the list of
>> domains to lookup. And the order of lookup.

> Not possible.

Yeah, dreams rarely come true. And often coming out weird, when they do.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 15.04.2014, <02:56>

Sorry for my terrible english...


--
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

  reply	other threads:[~2014-04-14 23:05 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 14:53 Corinna Vinschen
2014-04-10 15:19 ` Chris J. Breisch
2014-04-10 15:28   ` Corinna Vinschen
2014-04-10 18:39     ` Warren Young
2014-04-10 19:04       ` Corinna Vinschen
2014-04-10 20:21         ` Larry Hall (Cygwin)
2014-04-10 21:13         ` Eric Blake
2014-04-10 22:22           ` Warren Young
2014-04-11 12:22             ` Corinna Vinschen
2014-04-11 12:19           ` Corinna Vinschen
2014-04-13 10:35             ` Andrey Repin
2014-04-14  8:08               ` Corinna Vinschen
2014-04-14  9:05                 ` Andrey Repin
2014-04-13 10:35           ` Andrey Repin
2014-04-14  8:21             ` Corinna Vinschen
2014-04-10 17:21 ` Ken Brown
2014-04-10 17:49   ` Corinna Vinschen
2014-04-13 10:50     ` Andrey Repin
2014-04-14  8:24       ` Corinna Vinschen
2014-04-10 18:42 ` Warren Young
2014-04-10 19:11   ` Corinna Vinschen
2014-04-10 19:16     ` Corinna Vinschen
2014-04-11  2:17     ` Duncan Roe
2014-04-11  3:47       ` Warren Young
2014-04-11  6:20         ` Duncan Roe
2014-04-11 12:39           ` Corinna Vinschen
2014-04-12  0:06             ` Duncan Roe
2014-04-10 19:46 ` Achim Gratz
2014-04-10 20:24   ` Eric Blake
2014-04-11 12:45     ` Corinna Vinschen
2014-04-11 12:43   ` Corinna Vinschen
2014-04-11 23:36 ` Ken Brown
2014-04-12 11:13   ` Corinna Vinschen
2014-04-12 14:20     ` Ken Brown
2014-04-12 14:37       ` Corinna Vinschen
2014-04-15 21:15       ` Ken Brown
2014-04-16  8:04         ` Corinna Vinschen
2014-04-16  9:35           ` Corinna Vinschen
2014-04-16 15:28             ` Ken Brown
2014-04-16 15:32               ` Ken Brown
2014-04-16 15:43                 ` Corinna Vinschen
2014-04-13 10:20 ` Andrey Repin
2014-04-14  8:35   ` Corinna Vinschen
2014-04-14  9:20     ` Andrey Repin
2014-04-14 10:24       ` Corinna Vinschen
2014-04-14 23:05         ` Andrey Repin [this message]
2014-04-15  8:37           ` 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=205466581.20140415030052@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --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).