From owner-freebsd-security Tue Nov 4 16:19:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA21093 for security-outgoing; Tue, 4 Nov 1997 16:19:12 -0800 (PST) (envelope-from owner-freebsd-security) Received: from helium.vapornet.com (root@helium.vapornet.com [208.202.126.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA21050 for ; Tue, 4 Nov 1997 16:17:28 -0800 (PST) (envelope-from john@helium.vapornet.com) Received: from argon.vapornet.com (vapornet.xnet.com [205.243.141.107]) by helium.vapornet.com (8.8.7/VaporServer-v3.0+SpamNot) with ESMTP id SAA25485 for ; Tue, 4 Nov 1997 18:17:28 -0600 (CST) Received: by argon.vapornet.com (8.8.7/VaporClient-1.1) id SAA00712; Tue, 4 Nov 1997 18:17:11 -0600 (CST) Date: Tue, 4 Nov 1997 18:17:11 -0600 (CST) Message-Id: <199711050017.SAA00712@argon.vapornet.com> From: John Preisler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-security@freebsd.org Subject: norfork hole X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk last i heard about the norfork hole was the lkm to patch. Has this issue been resolved? -jrp