From owner-freebsd-security Mon Sep 18 10:57:27 2000 Delivered-To: freebsd-security@freebsd.org Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by hub.freebsd.org (Postfix) with ESMTP id 9DC0737B423; Mon, 18 Sep 2000 10:57:21 -0700 (PDT) Received: from grosse.bisbee.fugue.com (a40.pm3-32.theriver.com [206.102.192.104]) by toccata.fugue.com (8.9.3/8.6.11) with ESMTP id HAA03480; Sun, 17 Sep 2000 07:21:54 -0700 (PDT) Received: from grosse.bisbee.fugue.com (localhost [127.0.0.1]) by grosse.bisbee.fugue.com (8.11.0/8.6.11) with ESMTP id e8IHutw00575; Mon, 18 Sep 2000 10:56:57 -0700 (MST) Message-Id: <200009181756.e8IHutw00575@grosse.bisbee.fugue.com> To: Roman Shterenzon Cc: obrien@freebsd.org, freebsd-security@freebsd.org Subject: Re: ports/dhcp3: memory hole in dhclient In-Reply-To: Message from Roman Shterenzon of "Mon, 18 Sep 2000 10:21:05 +0200." Date: Mon, 18 Sep 2000 10:56:55 -0700 From: Ted Lemon Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The current version in ports seems to be dhcp-3.0b1pl17. > It wasn't touched for a month and dhcp-3.0b2pl4.tar.gz was released 4 days > ago, so you must be mistaken. I think you mistake me. I am using the word "current version" to refer to the most recent version released by the author of the software (me), not the most recent version in the FreeBSD ports collection. It's not helpful to tell me there are bugs in my code when you're not running the current version of my code. > Which version has the memory leaks fixed then? > I was just going to installs dhcpd 3 for dynamic dns updates, but now I'm > not so sure. Does dhcp server leaks memory as well? 3.0b2pl4. However, 3.0b2pl4 is a fairly raw beta, and there are a couple of known problems with it. If you need to be running something in production, I'd suggest you wait a bit. OTOH, free software improves when people try it and report bugs, so you've got a bit of a Catch-22 going there. :'} _MelloN_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message