From owner-freebsd-security Thu Dec 2 10:30:53 1999 Delivered-To: freebsd-security@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id C99F214CC4; Thu, 2 Dec 1999 10:30:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA87172; Thu, 2 Dec 1999 10:29:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Sheldon Hearn Cc: Steve Reid , Bill Swingle , security@FreeBSD.ORG, Jordan Hubbard Subject: Re: [btellier@USA.NET: Several FreeBSD-3.3 vulnerabilities] In-reply-to: Your message of "Thu, 02 Dec 1999 13:24:58 +0200." <67349.944133898@axl.noc.iafrica.com> Date: Thu, 02 Dec 1999 10:29:28 -0800 Message-ID: <87169.944159368@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If you're not going to badger a port's maintainer until he/she does > something, you're unlikely to get results out of a single request. > That's why the PR system is good. The PR sits there pissing us off > until someone does something about it. :-) Well, let me just add something to this, and that's that if you also can't get reasonable satisfaction out of a maintainer, move up the "chain of authority" and talk to the ports team and/or Satoshi Asami about it. If that still doesn't net you results, appeal to core. The buck will eventually stop somewhere. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message