public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/15374] New: Make getent services compliant with RFC 6335 section 5.1
@ 2013-04-17  9:16 cambridge at users dot sf.net
  2013-11-07 11:52 ` [Bug libc/15374] " neleai at seznam dot cz
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: cambridge at users dot sf.net @ 2013-04-17  9:16 UTC (permalink / raw)
  To: glibc-bugs

http://sourceware.org/bugzilla/show_bug.cgi?id=15374

             Bug #: 15374
           Summary: Make getent services compliant with RFC 6335 section
                    5.1
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: cambridge@users.sf.net
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


RFC 6335 section 5.1 permits service names with leading digits.

nss/getent.c does not, as they would be treated as port numbers:

 791       if (isdigit (key[i][0]))
 792         serv = getservbyport (htons (atol (key[i])), proto);
 793       else
 794         serv = getservbyname (key[i], proto);

Checking IANA, there are currently 28 service names registered that begin with
a digit, for example 3com-tsmux and 3gpp-cbsp.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libc/15374] Make getent services compliant with RFC 6335 section 5.1
  2013-04-17  9:16 [Bug libc/15374] New: Make getent services compliant with RFC 6335 section 5.1 cambridge at users dot sf.net
@ 2013-11-07 11:52 ` neleai at seznam dot cz
  2013-11-07 11:52 ` cvs-commit at gcc dot gnu.org
  2014-06-13 10:09 ` fweimer at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: neleai at seznam dot cz @ 2013-11-07 11:52 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=15374

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |neleai at seznam dot cz
         Resolution|---                         |FIXED

--- Comment #2 from Ondrej Bilka <neleai at seznam dot cz> ---
Fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libc/15374] Make getent services compliant with RFC 6335 section 5.1
  2013-04-17  9:16 [Bug libc/15374] New: Make getent services compliant with RFC 6335 section 5.1 cambridge at users dot sf.net
  2013-11-07 11:52 ` [Bug libc/15374] " neleai at seznam dot cz
@ 2013-11-07 11:52 ` cvs-commit at gcc dot gnu.org
  2014-06-13 10:09 ` fweimer at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2013-11-07 11:52 UTC (permalink / raw)
  To: glibc-bugs

http://sourceware.org/bugzilla/show_bug.cgi?id=15374

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
       via  e4368156e64e04a204d832351abcb535572eb919 (commit)
      from  8d6bb57c44557c344d56653c3380885bf1dcabd7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e4368156e64e04a204d832351abcb535572eb919

commit e4368156e64e04a204d832351abcb535572eb919
Author: Ondřej Bílka <neleai@seznam.cz>
Date:   Thu Nov 7 12:46:57 2013 +0100

    Make getent services compliant with  RFC 6335 section 5.1 Fixes bug 15374

    The RFC 6335 allows services that start with digit (like 3com-tsmux).
    These were parsed as port number which this patch fixes.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog    |    5 +++++
 NEWS         |   14 +++++++-------
 nss/getent.c |    8 ++++++--
 3 files changed, 18 insertions(+), 9 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-20089-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Nov 07 12:30:01 2013
Return-Path: <glibc-bugs-return-20089-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 23463 invoked by alias); 7 Nov 2013 12:30:00 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 23420 invoked by uid 55); 7 Nov 2013 12:29:57 -0000
From: "keld at keldix dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/14641] Add a strftime()-like function for formatting human names
Date: Thu, 07 Nov 2013 12:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: keld at keldix dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-14641-131-dlhH3BMJWf@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14641-131@http.sourceware.org/bugzilla/>
References: <bug-14641-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-11/txt/msg00060.txt.bz2
Content-length: 3030

http://sourceware.org/bugzilla/show_bug.cgi?id\x14641

--- Comment #10 from keld at keldix dot com <keld at keldix dot com> ---
On Thu, Nov 07, 2013 at 02:26:39AM +0000, bugdal at aerifal dot cx wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id\x14641
>
> --- Comment #9 from Rich Felker <bugdal at aerifal dot cx> ---
> On Wed, Nov 06, 2013 at 11:57:48PM +0000, keld at keldix dot com wrote:
> > The intended use is then to switch to the locale of the address in question,
> > for eg formatting of an address for a postal letter.
>
> This is not the way locales are supposed to be used. You don't just
> keep switching them around at runtime. In your specific example of
> formatting a letter, it's wrong, because you want the address
> formatted according to the cultural conventions of the place in which
> it's being sent, but the name written the way the recipient's name is
> supposed to be written.

If there are different users then it is only natural to switch to each user's
locale, eg when printing a name, or printing an address.
When printing a namei in an address, one should  follw the IPU standard
for this. This standard has several options. Either French or the local
language of the receiving country. And then there may be
more than one convention in a country, eg with multiple official langages.

A recipient may want a name to be wrttten in ways. Eg in the  Chinese, Indian,
Arabic
or the Latin script. Also dependent on script the family name could be placed
first or last.
Even with the Latin script, sometimes the family name is written first.
Or the family name is written in all capitals.

> > To find the correct locale for a given address is not straightforward.
> > You would often have a country associated with the address and then you could
> > find a locale related to that country.
>
> But that has nothing to do with how the name should be formatted, only
> with how the address should be formatted. Also, depending on your
> locale, the matter of formatting an address can depend on the
> conventions of the recipient's country or the sender's. In any case
> this logic is all way outside the scope of libc locale.

Yes it is mostly how the address should be formatted. But it could also
be used for the name formatting, eg in a letter, where you have written the
text
in the language of the receiver, and you also want to format the name in that
language.


I believe this is in scope of libc, meaning that this is to make an application
culturally adaptable. It is just a more advanced use than the normal i18n,
because we want to accomodate different users' cultural conventions.

Still, it can be used just for one set of user preferences,
eg in my country, Denmark, if I would send out a letter to many
people, they would almost all be Danish, and then a few Sewdes  and Norwegians
and possibly German adressees, who share the same cultural conventions
wrt naming and addresses.

best regards
keld

--
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libc/15374] Make getent services compliant with RFC 6335 section 5.1
  2013-04-17  9:16 [Bug libc/15374] New: Make getent services compliant with RFC 6335 section 5.1 cambridge at users dot sf.net
  2013-11-07 11:52 ` [Bug libc/15374] " neleai at seznam dot cz
  2013-11-07 11:52 ` cvs-commit at gcc dot gnu.org
@ 2014-06-13 10:09 ` fweimer at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: fweimer at redhat dot com @ 2014-06-13 10:09 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=15374

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-06-13 10:09 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-17  9:16 [Bug libc/15374] New: Make getent services compliant with RFC 6335 section 5.1 cambridge at users dot sf.net
2013-11-07 11:52 ` [Bug libc/15374] " neleai at seznam dot cz
2013-11-07 11:52 ` cvs-commit at gcc dot gnu.org
2014-06-13 10:09 ` fweimer at redhat dot com

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