From owner-freebsd-security Sun May 21 22:19: 2 2000 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5632E37B7AB for ; Sun, 21 May 2000 22:18:59 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA04569; Sun, 21 May 2000 23:18:57 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id XAA67456; Sun, 21 May 2000 23:18:37 -0600 (MDT) Message-Id: <200005220518.XAA67456@billy-club.village.org> To: Brett Glass Subject: Re: The procfs Hole in 2.2.8-STABLE? Cc: cjclark@home.com, freebsd-security@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 May 2000 22:58:57 MDT." <4.3.1.2.20000521225733.048a0c40@localhost> References: <4.3.1.2.20000521225733.048a0c40@localhost> <20000521140847.G96573@cc942873-a.ewndsr1.nj.home.com> Date: Sun, 21 May 2000 23:18:37 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <4.3.1.2.20000521225733.048a0c40@localhost> Brett Glass writes: : Hopefully, some of the things that are being fixed in 4.0 will : be backported to 3.5. We want 3.5 to be the "golden" release that : we use for production until 4.2 is ready and stable. 4.1 should be golden enough for production in even the most demanding environments. That said, as far as I know people have been good and backported all relevant security fixes made to 4.0 back to the 3.x branch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message