From owner-freebsd-questions Sun Nov 1 02:30:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09386 for freebsd-questions-outgoing; Sun, 1 Nov 1998 02:30:28 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from poseidon.host4u.net (poseidon.host4u.net [209.150.128.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09381 for ; Sun, 1 Nov 1998 02:30:27 -0800 (PST) (envelope-from dan.langille@dvl-software.com) Received: from wocker (210-55-210-87.ipnets.xtra.co.nz [210.55.210.87]) by poseidon.host4u.net (8.8.5/8.8.5) with SMTP id EAA04165 for ; Sun, 1 Nov 1998 04:30:21 -0600 Message-Id: <199811011030.EAA04165@poseidon.host4u.net> From: "Dan Langille" Organization: DVL Software Limited To: questions@FreeBSD.ORG Date: Sun, 1 Nov 1998 23:30:19 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: how to determine if a bug has been fixed Reply-to: dan.langille@dvl-software.com X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was looking at "Incomplete List of UNIX Vulnerabilities" (http://www.cs.iastate.edu/~ghelmer/unixsecurity/unix_vuln.html) when I had a thought. How can I find out if a given bug listed there has been repaired? (with respect to FreeBSD). -- Dan Langille DVL Software Limited http://www.racingsystem.com : for race timing solutions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message