public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tony dot shadwick at usa dot gknaerospace dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/11924] New: Gecos parsing with g_get_real_name causes headaches with network authentication. Date: Wed, 18 Aug 2010 20:01:00 -0000 [thread overview] Message-ID: <20100818200117.11924.tony.shadwick@usa.gknaerospace.com> (raw) I could go through a whole lot of repetition, but the entirety of this problem is synopsized elsehwere by me: https://bugs.launchpad.net/indicator-applet/+bug/484238 The short version is that g_get_real_name parses the gecos field up to the first comma. The problem is that when tying into a network authentication schemes, often you will have the format last name, first name. g_get_real_name blindly presumes that you have legacy gecos data there: "Interpretation of the gecos field varies between systems, but traditionally holds 4 comma-separated fields containing the user's full name, office location, work phone number, and home phone number. An & in the gecos field should be replaced by the user's properly capitalized login name ." Of course things like a Windows domain could care less about this. The only solution I could come up with was to count commas. If there's only one comma there, presume that it's part of the name. In my case, right now my gecos field has "Shadwick, Tony" since I use likewise-open for authentication. g_get_real_name returns "Shadwick". Now if I had Shadwick, Tony,, Then I might understand. Reality is that in situations where legacy data gets entered (such as local authentication systems), the blank fields are present with repeating commas. I struggle to find a situation where the commas are present without legacy GECOS data being there. I'm open to alternatives to this, but it is a bit of a problem. -- Summary: Gecos parsing with g_get_real_name causes headaches with network authentication. Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: tony dot shadwick at usa dot gknaerospace dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11924 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-08-18 20:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-18 20:01 tony dot shadwick at usa dot gknaerospace dot com [this message] 2010-08-19 8:31 ` [Bug libc/11924] " schwab at linux-m68k dot org 2010-08-19 13:56 ` tony dot shadwick at usa dot gknaerospace dot com
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=20100818200117.11924.tony.shadwick@usa.gknaerospace.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).