From owner-freebsd-security Sat Mar 24 0:25:15 2001 Delivered-To: freebsd-security@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [205.178.102.196]) by hub.freebsd.org (Postfix) with ESMTP id CCA7837B71B for ; Sat, 24 Mar 2001 00:25:06 -0800 (PST) (envelope-from pjklist@ekahuna.com) Received: from pc-02 (pc02.ekahuna.com [205.178.102.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sat, 24 Mar 2001 00:25:06 -0800 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: security@FreeBSD.ORG Date: Sat, 24 Mar 2001 00:25:06 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Delayed security advisories Reply-To: pjklist@ekahuna.com Message-ID: <3ABBE962.21950.29D4882@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org See message snippet included below. Can someone tell me why there are security advisories coming out now for security vulnerabilities known to have been corrected 3 months ago? Phil > Date: Thu, 22 Mar 2001 13:12:32 -0800 (PST) > From: FreeBSD Security Advisories > Subject: FreeBSD Security Advisory FreeBSD-SA-01:30.ufs-ext2fs > > - -----BEGIN PGP SIGNED MESSAGE----- > > ============================================================================= > FreeBSD-SA-01:30 Security Advisory > FreeBSD, Inc. > > Topic: UFS/EXT2FS allows disclosure of deleted data > > Category: kernel > Module: ufs/ext2fs > Announced: 2001-03-22 > Credits: Sven Berkvens , Marc Olzheim > Affects: All released versions of FreeBSD 3.x, 4.x. > FreeBSD 3.5-STABLE prior to the correction date. > FreeBSD 4.2-STABLE prior to the correction date. > Corrected: 2000-12-22 (FreeBSD 3.5-STABLE) > 2000-12-22 (FreeBSD 4.2-STABLE) > FreeBSD only: NO -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message