From owner-freebsd-security Sat Apr 15 19:39:21 2000 Delivered-To: freebsd-security@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id CD04837B8DA for ; Sat, 15 Apr 2000 19:39:14 -0700 (PDT) (envelope-from will@blackdawn.com) Received: from argon.blackdawn.com (01-037.dial.008.popsite.net [209.69.194.37]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id TAA31900; Sat, 15 Apr 2000 19:39:10 -0700 (PDT) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 9604F18B9; Sat, 15 Apr 2000 22:39:00 -0400 (EDT) Date: Sat, 15 Apr 2000 22:39:00 -0400 From: Will Andrews To: "Andrey A. Chernov" Cc: security@FreeBSD.ORG Subject: Re: Re-enabling lynx-current again Message-ID: <20000415223900.H33593@argon.blackdawn.com> References: <20000416062109.A28187@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000416062109.A28187@nagual.pp.ru>; from ache@nagual.pp.ru on Sun, Apr 16, 2000 at 06:21:09AM +0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 16, 2000 at 06:21:09AM +0400, Andrey A. Chernov wrote: > As I see in lynx CHANGES file, buffer overflows fixed at 2000-03-26 > (2.8.3dev.23). Is this step solve known problems? I plan to re-enable > lynx-current, if nobody disagree. If you are CERTAIN that these security holes have been fixed, then by all means re-enable lynx. But make sure they are, before you update the lynx port. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message