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]
Message-ID: <OFB5D50B53.A24A00A2-ON88257303.0017FE53-88257303.0018AD5D@us.ibm.com>
Date:	Fri, 22 Jun 2007 21:30:05 -0700
From:	David Stevens <dlstevens@...ibm.com>
To:	Simon Arlott <simon@...e.lp0.eu>
Cc:	"C. Scott Ananian" <cscott@...top.org>, netdev@...r.kernel.org,
	netdev-owner@...r.kernel.org
Subject: Re: [RFD] First draft of RDNSS-in-RA support for IPv6 DNS autoconfiguration

netdev-owner@...r.kernel.org wrote on 06/22/2007 06:17:46 PM:

> On 23/06/07 02:04, David Stevens wrote:
> >         Why not make the application that writes resolv.conf
> > also listen on a raw ICMPv6 socket? I don't believe you'd need
> > any kernel changes, then, and it seems pretty simple and
> > straightforward.
> 
> Because then it requires yet another network daemon, RA in 
> the kernel means there's no need for one to manage adding 
> auto-configured IP addresses... what's wrong with doing the 
> same for DNS?

        It's not yet another one, since you have to run something
to get it in resolv.conf, anyway. That seems much better to me
than having the kernel track data that can only be used at the
application layer. The app itself looks like it'd be really simple.
        Auto-configured addresses are used by the kernel. It has to
have those addresses. But the kernel doesn't do DNS look-ups, or
write resolv.conf; that's the difference, for me.

                                                                +-DLS

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ