Date: Tue, 7 Feb 2006 08:50:25 -0800 From: "David W. Hankins" <David_Hankins@isc.org> To: freebsd-stable@freebsd.org Subject: Re: dhclient in 6.0 Message-ID: <20060207165025.GB23573@isc.org> In-Reply-To: <200602061111.46404.matt@mattsnetwork.co.uk> References: <20060205060416.3C11045041@ptavv.es.net> <200602060802.16643.matt@mattsnetwork.co.uk> <7.0.0.16.2.20060206205810.02239b00@mailshack.com> <200602061111.46404.matt@mattsnetwork.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Feb 06, 2006 at 11:11:45AM +0000, Matt Dawson wrote:
> send host-name `hostname -s`;
I currently have *three* competing "execute()" patches queued for ISC
DHCP 3.1.0 which could be used to do this:
send host-name execute("hostname -s");
send fqdn.fqdn execute("hostname");
send fqdn.encoded on;
send fqdn.server_update [off/on];
do-forward-updates [opposite of fqdn.server_update];
ISC dhclient also doesn't identify itself uniquely in the vendor-class-id
option...this to my knowledge hasn't been a problem since no one seems
to need to configure server-specific workarounds for the ISC dhclient.
If they had to, they also wouldn't be able to, is what I mean.
The point is we could also produce a vendor-id like;
send vendor-class-identifier concat("ISC DHCP 3.1.x - ",
execute("uname -s -r -m"));
Which, I might point out, is similar to dhcpcd's default behaviour.
We could also easily do both of these by default. No problem. We could
even enclose the host-name in a conditional to detect unset hostnames so
you don't get eight boxes claiming to be "default".
But these are privacy questions more than technical ones.
Is it right to default to less privacy in this case?
--=20
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD6M/RcXeLeWu2vmoRAtMDAJwMrZBV6NotzB4yqKIL6urLJU2hwACfWjvT
patXiLW33evVA4NdeYpDEhA=
=Hr1c
-----END PGP SIGNATURE-----
--W/nzBZO5zC0uMSeA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060207165025.GB23573>