From owner-freebsd-security Thu Jul 13 11:14:23 2000 Delivered-To: freebsd-security@freebsd.org Received: from faith.cs.utah.edu (faith.cs.utah.edu [155.99.198.108]) by hub.freebsd.org (Postfix) with ESMTP id 4715E37C50A for ; Thu, 13 Jul 2000 11:14:18 -0700 (PDT) (envelope-from danderse@cs.utah.edu) Received: (from danderse@localhost) by faith.cs.utah.edu (8.9.3/8.9.3) id MAA22497; Thu, 13 Jul 2000 12:14:09 -0600 (MDT) Message-Id: <200007131814.MAA22497@faith.cs.utah.edu> Subject: Re: Two kinds of advisories? To: brett@lariat.org (Brett Glass) Date: Thu, 13 Jul 2000 12:14:09 -0600 (MDT) Cc: security@FreeBSD.ORG In-Reply-To: <4.3.2.7.2.20000713120631.04d53b60@localhost> from "Brett Glass" at Jul 13, 2000 12:12:11 PM From: "David G. Andersen" X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org That's a matter of client education, and it's not going to be fixed by changing the subject. The subject of the matter is the FreeBSD ports collection. The disclaimer in the message is a pretty good place to start educating your clients. -Dave Lo and behold, Brett Glass once said: > > I've recently added some of my clients to the Bugtraq mailing list, and > whenever a message goes out with a subject like "FreeBSD Ports Security > Advisory: ," they think it's a security hole in FreeBSD. Of course, > WE know it's not, but they don't understand what "FreeBSD Ports" means and > get the wrong idea. Any ideas about how to rephrase the subject lines so > that people who see these messages will get the right idea without knowing > what the Ports Collection is? Perhaps if the name "FreeBSD" didn't come first? > > --Brett > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > -- work: dga@lcs.mit.edu me: dga@pobox.com MIT Laboratory for Computer Science http://www.angio.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message