From owner-freebsd-security Mon Oct 27 01:41:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA00333 for security-outgoing; Mon, 27 Oct 1997 01:41:56 -0800 (PST) (envelope-from owner-freebsd-security) Received: from axl.iafrica.com (axl.iafrica.com [196.31.1.167]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA00290 for ; Mon, 27 Oct 1997 01:40:22 -0800 (PST) (envelope-from sheldonh@axl.iafrica.com) Received: from axl.iafrica.com (localhost [127.0.0.1]) by axl.iafrica.com (8.8.7/8.8.7) with ESMTP id LAA21599 for ; Mon, 27 Oct 1997 11:39:42 +0200 (SAT) (envelope-from sheldonh@axl.iafrica.com) From: Sheldon Hearn To: freebsd-security@freebsd.org Subject: 2.2.5-RELEASE ERRATA.TXT Date: Mon, 27 Oct 1997 11:39:39 +0200 Message-ID: <21595.877945179@axl.iafrica.com> Sender: owner-freebsd-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems a little unfair to be pissing in the faces of users who don't check the ERRATA.TXT for 2.2.5-RELEASE before asking about security issues like the open() syscall and whether their fixes made it into the release when said errata file is empty. There is a reference to ftp://freebsd.org/pub/CERT/ in the ERRATA.TXT file but the most recent bug at this location is the procfs hole. :) 2c.sheldonh Sheldon Hearn (FreeBSD 2.2-STABLE User) ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/ERRATA.TXT This file contains post-release ERRATA for 2.2.5 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. For 2.2.5 security advisories, see: ftp://freebsd.org/pub/CERT/ For the latest information (note the URL carefully - this is NOT ftp.freebsd.org). ---- Current active security advisories for 2.2.5: None ---- ERRATA: No known errata at this time.