Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Aug 2000 14:43:01 +0200
From:      Shaun Jurrens <shaun@shamz.net>
To:        Kris Kennaway <kris@FreeBSD.org>
Cc:        freebsd-security@FreeBSD.org
Subject:   Re: FreeBSD Security Advisory: FreeBSD-SA-00:34.dhclient
Message-ID:  <20000815144301.D7893@atreides.freenix.no>
In-Reply-To: <Pine.BSF.4.21.0008150419280.21436-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Tue, Aug 15, 2000 at 04:21:43AM -0700
References:  <20000815131625.C7893@atreides.freenix.no> <Pine.BSF.4.21.0008150419280.21436-100000@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 15, 2000 at 04:21:43AM -0700, Kris Kennaway wrote:
#> On Tue, 15 Aug 2000, Shaun Jurrens wrote:
#> 
#> > Hi,
#> > 
#> > I wrote David O'Brien a few weeks ago asking about the merge of the post
#> > 2.0p12 back to 3-STABLE and he said he had no boxes to test it on.  I will
#> > try to grab the code directly from my 4-STABLE box and see if it builds
#> > correctly.

	Simply copying the src from contrib from my 4-STABLE (cvsup 12Aug) box
	to my 3.5 box as well as the Makefile from /usr/src/sbin/dhclient
	compiled and installed successfully.  Should have gotten around to it
	when I first saw the PR.  Hope this helps.  Seems to be working
	correctly as well.
#> 
#> Yeah, that was the aforementioned logistical difficulty. I understand BSDi
#> are going to be setting up a 3.x build machine for the developers to use,
#> but it hasn't happened yet, and most of the developers have no 3.x
#> machines to test this on their own.
#> 
#> > Just a note: the isc-dhcp2 port has the client build commented out.  I am
#> > currently trying to get it to build, but am running into problems on my 3.5
#> > box. So afaics, the proposed solution of using the dhclient binary from the
#> > port isn't a viable solution until someone changes patch-aa and then gets
#> > the client to build correctly.
#> 
#> Ah, I forgot about this (it was a deliberate change since we have the
#> client in the base and so theres no point in building it in the port as
#> well). Well, I guess that option is out..I'll update the advisory.
#> 
#> Kris
#> 
	Btw, I never did get the client part in the port to work, but the
	other way was essentially easier, so I stopped wasting my time on it.

-- 
Yours truly,

Shaun D. Jurrens
shaun@shamz.net
shamz@freenix.no


IRCNET nick: shamz #chillout #unix #FreeBSD


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000815144301.D7893>