public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gecos from AD? (was Re: timeout in LDAP access)
Date: Wed, 18 Jun 2014 08:38:00 -0000	[thread overview]
Message-ID: <20140618083837.GW23700@calimero.vinschen.de> (raw)
In-Reply-To: <8E2EDB1F-9A60-488B-929F-7E62C0808A3E@Denis-Excoffier.org>

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

On Jun 18 00:59, Denis Excoffier wrote:
> On 2014-06-17 12:30, Corinna Vinschen wrote:
> > On Jun 17 12:00, Corinna Vinschen wrote:
> >> On Jun 16 22:39, Denis Excoffier wrote:
> >>> Another (unrelated and less important) problem is that 'getent'
> >>> happily produces lines with some extra ‘:’, in particular when the
> >>> gecos field itself contains ‘:’.
> >> 
> >> Wow, that *is* important.  All fields returned from the server have to
> >> get their colons converted to commas.  I'll fix that.
> > 
> > While we're at it... do we really need the gecos info?  Cygwin fills
> > out this field with the Windows username and SID info for internal
> > purposes, and then adds the gecos info from AD.  However, it's just
> > informational and usually only used by the finger(1) tool.
> The gecos field from AD seems to be _prepended_ (not appended) to the
> username + SID.

Right, I just wasn't going for details.  The content of gecos is added
to the pw_gecos field, one way or another.

> In any case, it may represent some information with
> high added value (like user real name or e-mail address, depending on
> local rules of course). I would not vote for removing it.
> 
> Why is it so clear that the ‘:’ should be replaced by a comma? Here, we
> have situations where it contains something
> like « Owner: Albert Einstein ». An underscore could be more appropriate.

The point is, the colon must be replaced with some other ASCII char.
I'm pretty sure this doesn't deserve another nsswitch.conf setting.
So we just choose *some* ASCII char and be done with it.  I don't like
the underscore but maybe space is ok.  Or semicolon.

> There is something more important: i’ve written in one of my previous
> messages that when ‘:’ occurs in gecos, the resulting ‘passwd’ file under
> ‘getent’ will contain more ‘:’ than expected, but this is incorrect. In fact
> (and i would like someone to try it), when ‘:’ is found within the
> gecos field, ‘getent’ does not show the last (homedir) field, and
> the count of ‘:’ is still correct. The problem might not be in getent after
> all.

Sure.  It's all occuring inside the Cygwin DLL.


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-06-18  8:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 20:39 timeout in LDAP access Denis Excoffier
2014-06-17 10:00 ` Corinna Vinschen
2014-06-17 10:30   ` gecos from AD? (was Re: timeout in LDAP access) Corinna Vinschen
2014-06-17 12:51     ` Corinna Vinschen
2014-06-17 23:07       ` Denis Excoffier
2014-06-18  2:18       ` AW: " Christoph H. Hochstaetter
2014-06-17 22:59     ` Denis Excoffier
2014-06-18  8:38       ` Corinna Vinschen [this message]
2014-06-17 22:41   ` timeout in LDAP access Denis Excoffier
2014-06-18  8:33     ` Corinna Vinschen
2014-06-18 18:01       ` Corinna Vinschen
2014-06-19 17:53         ` Denis Excoffier
2014-06-23  9:10           ` Corinna Vinschen
2014-06-23 20:38             ` Denis Excoffier
2014-06-24 15:59               ` Corinna Vinschen
2014-06-25 10:15                 ` Corinna Vinschen
2014-06-25 20:44                   ` Denis Excoffier
2014-06-25 21:14                     ` Corinna Vinschen
2014-07-03 20:57                       ` Denis Excoffier
2014-07-07 11:07                         ` Corinna Vinschen
2014-07-08 19:34                           ` Denis Excoffier
2014-07-09 10:13                             ` Corinna Vinschen
2014-07-12 13:39                               ` Denis Excoffier
2014-07-14  9:51                                 ` Corinna Vinschen
2014-07-14 13:48                                   ` Corinna Vinschen
2014-07-15 16:29                                     ` Denis Excoffier
2014-07-15 18:20                                       ` Andrey Repin
2014-07-16 13:52                                       ` Corinna Vinschen
2014-07-17  6:33                                         ` Denis Excoffier
2014-07-18 19:18                                           ` Corinna Vinschen
2014-07-28  9:21                                             ` Corinna Vinschen
2014-07-28 18:51                                               ` Denis Excoffier
2014-07-29  9:07                                                 ` Please test AD integration changes, documentation attached (was Re: timeout in LDAP access) 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=20140618083837.GW23700@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).