From owner-freebsd-security Mon Jan 24 18: 9:46 2000 Delivered-To: freebsd-security@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8B23215978 for ; Mon, 24 Jan 2000 18:09:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA94595; Mon, 24 Jan 2000 18:09:37 -0800 (PST) (envelope-from dillon) Date: Mon, 24 Jan 2000 18:09:37 -0800 (PST) From: Matthew Dillon Message-Id: <200001250209.SAA94595@apollo.backplane.com> To: Michael Oswell Cc: Warner Losh , Tim Yardley , freebsd-security@FreeBSD.ORG Subject: Re: Fwd: *BSD procfs vulnerability References: Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :I've manually taken the information from the 3.x patch and used it to :patch a 2.2.7 box we had here. It appears to work, though all I have done :to test this is run the exploit script that was sent to bugtraq. : :I have also run the patch against a 2.2.8 box successfully (and recompiled :the kernel), though have yet to reboot to the box to be sure it works. : :The actual code in the patch below is identical to the one that was :released for 3.2 (just manually inserted instead of using patch). Like I :said, it appears to work here, though I make no guarentees to anyone that :this is the best or correct way to patch the 2.2.x kernels for this bug. Excelllent! I am going to wait a maximum of a few days to see if my old ISP gets the patch in to give us some corroboration, then will commit this into the 2.2.x tree. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message