public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: More testing needed: New passwd/group AD/SAM integration
Date: Wed, 14 May 2014 15:10:00 -0000	[thread overview]
Message-ID: <20140514150654.GF2436@calimero.vinschen.de> (raw)
In-Reply-To: <f5bvbt8e9ao.fsf@troutbeck.inf.ed.ac.uk>

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

On May 14 15:15, Henry S. Thompson wrote:
> Corinna Vinschen writes:
> 
> > Yes, I noticed the "s".  But I missed to explain that I wasn't talking
> > about the delay.  What I can't reproduce is that `id Administrators'
> > returns a result:
> >
> >   $ id +Administrators
> >   uid=544(+Administrators) gid=544(+Administrators) groups=11(+Authenticated Users),544(+Administrators)
> >
> > but:
> >
> >   $ id Administrators
> >   id: Administrators: no such user
> >
> > But now I understand why this occurs.  It's the different handling of
> > account names without domain prefix on standalone vs. domain machines.
> > I applied a patch now which checks the incoming names for validity under
> > the current naming rules, so, in theory, `id Administrators' should now
> > return "no such user" for you as well.
> 
> > I just created new snapshots on http://cygwin.com/snapshots/
> > Please give'em a try.
> 
> Done, and now
> 
>  [x86_64 20140514]> id Administrators
>  id: Administrators: no such user
>  [x86_64 20140514]> +Administrators
>  uid=544(+Administrators) gid=544(+Administrators) groups=11(+Authenticated Users),544(+Administrators)
> 
> with no delay in either case.  So _that's_ sorted.
> 
> Overall, I now get the following clean pattern of id behaviour
> wrt prefix '+':
> 
>                 w/o      w
>                  +       +
> SYSTEM          no      yes
> LocalService    no      yes
> NetworkService  no      yes
> Administrators  no      yes
> TrustedInstaller no      yes
> Administrator   yes     no
> cyg_server      yes     no
> Guest           yes     no
> ht              yes     no
> postgres        yes     no
> sshd            yes     no
> 
> [you can reproduce this using
>   > cut -d ':' -f 1 /etc/passwd | while read u; do echo -n "$u  "; if id $u >/dev/null 2>/dev/null; then echo -n "yes	"; else echo -n "no	"; fi;if id '+'$u >/dev/null 2>/dev/null; then echo "yes"; else echo "no"; fi done
> ]

Thanks for testing.  If you find any other problems or annoyances,
please speak up.


Thanks,
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-05-14 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 11:05 Corinna Vinschen
2014-05-13 12:19 ` Henry S. Thompson
2014-05-13 14:53   ` Corinna Vinschen
2014-05-13 16:30     ` Corinna Vinschen
2014-05-13 16:41       ` Henry S. Thompson
2014-05-13 16:44         ` Corinna Vinschen
2014-05-13 18:00           ` Henry S. Thompson
2014-05-13 19:20             ` Corinna Vinschen
2014-05-13 21:28               ` Henry S. Thompson
2014-05-14 12:59                 ` Corinna Vinschen
2014-05-14 14:58                   ` Henry S. Thompson
2014-05-14 15:10                     ` Corinna Vinschen [this message]
2014-05-16 22:08                       ` Chris J. Breisch
2014-05-17 10:12                         ` 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=20140514150654.GF2436@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).