From owner-freebsd-security Sun May 3 14:39:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02548 for freebsd-security-outgoing; Sun, 3 May 1998 14:39:16 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from ns2.sminter.com.ar (ns2.sminter.com.ar [200.10.100.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02500 for ; Sun, 3 May 1998 14:39:02 -0700 (PDT) (envelope-from Recabarren!fpscha@ns2.sminter.com.ar) Received: (from uucp@localhost) by ns2.sminter.com.ar (8.8.5/8.8.4) id SAA26819 for freebsd.org!freebsd-security; Sun, 3 May 1998 18:37:26 -0300 (GMT) >Received: (from fpscha@localhost) by localhost.schapachnik.com.ar (8.8.5/8.8.5) id SAA00317; Sun, 3 May 1998 18:18:04 -0300 (ARST) From: "Fernando P. Schapachnik" Message-Id: <199805032118.SAA00317@localhost.schapachnik.com.ar> Subject: Why aren't security fixes posted to security-announce? To: freebsd-security@FreeBSD.ORG Date: Sun, 3 May 1998 18:18:04 -0300 (ARST) Reply-To: fpscha@schapachnik.com.ar X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk *** A similar message has already been posted some days before. As I didn't received it, I assume nobody has. Sorry if this is not the case. *** Hello: I like to know if there is a good reason for not posting to announce or security-announce those bugs/fixes mailed to security. I'm not talking about open issues that may help an attacker, but about those which has a fix or workaround. In this situation we can find Niall Smart's "Vulnerability in OpenBSD, FreeBSD-stable lprm", Dima Ruban's patch to BIND related with "Re: Any news on this?: CA-98.05 Multiple Vulnerabilities in BIND" and Vasim Valejev's "Example of RFC-1644 attack", just to quote a few I received in the past few weeks. Thanks and regards. Fernando P. Schapachnik fpscha@schapachnik.com.ar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message