From owner-freebsd-security Mon May 22 18:27: 2 2000 Delivered-To: freebsd-security@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id D2F6537B7AD for ; Mon, 22 May 2000 18:26:58 -0700 (PDT) (envelope-from fpscha@ns1.via-net-works.net.ar) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id WAA02250; Mon, 22 May 2000 22:26:15 -0300 (GMT) From: Fernando Schapachnik Message-Id: <200005230126.WAA02250@ns1.via-net-works.net.ar> Subject: Re: The procfs Hole in 2.2.8-STABLE? In-Reply-To: <200005221815.MAA96713@harmony.village.org> from Warner Losh at "May 22, 0 12:15:39 pm" To: imp@village.org (Warner Losh) Date: Mon, 22 May 2000 22:26:15 -0300 (GMT) Cc: cjclark@home.com, freebsd-security@FreeBSD.ORG Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org En un mensaje anterior, Warner Losh escribió: > We stopped committing to make backports to 2.x when FreeBSD 3.2 was > released, or about this time last year. Anything that happened after > that may or may not hav emade it back to 2.2.8. Also, some of them > weren't noteworthy at the time, so no advisory was issued (I had the > advisory setting too high). Some exploits have surfaced against old > versions of FreeBSD. There's no central collection of these > documented anywhere. I wish I had a better answer for you than this. Any of them is a remote exploit? Have an URL? Thanks! Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fernando@via-net-works.net.ar (54-11) 4323-3333 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message