linux-kernel - Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Mar 2011 15:25:18 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
	linux-arch@...r.kernel.org, linux-api@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate
 name service errors

On Tue, 08 Mar 2011 15:09:59 +0000
David Howells <dhowells@...hat.com> wrote:

> Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> 
> > > Define ENONAMESERVICE to indicate "Network name service unavailable".
> > > This can be used to indicate, for example, that an attempt was made by
> > > dns_query() to make a query, but the name server (e.g. a DNS server) it is
> > > supposed to contact didn't answer or that it couldn't determine the
> > > location of a suitable server.
> > 
> > Are these in glibc and are there glibc patches submitted and accepted for
> > this ?
> 
> No.
> 
> Are you saying that I should push them through glibc first - and then submit
> them to the kernel? 

I was wondering if at least there was some co-ordination going on so that
functions like perror() produced sensible answers. Otherwise it's
debatable if its actually an improvement for the poor end user ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/