Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Apr 2000 22:39:00 -0400
From:      Will Andrews <andrews@technologist.com>
To:        "Andrey A. Chernov" <ache@nagual.pp.ru>
Cc:        security@FreeBSD.ORG
Subject:   Re: Re-enabling lynx-current again
Message-ID:  <20000415223900.H33593@argon.blackdawn.com>
In-Reply-To: <20000416062109.A28187@nagual.pp.ru>; from ache@nagual.pp.ru on Sun, Apr 16, 2000 at 06:21:09AM %2B0400
References:  <20000416062109.A28187@nagual.pp.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <andrews@technologist.com>
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




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