From owner-freebsd-security Thu Jul 13 12:39:53 2000 Delivered-To: freebsd-security@freebsd.org Received: from ns1.uscreativetypes.com (ns1.uscreativetypes.com [199.45.183.33]) by hub.freebsd.org (Postfix) with ESMTP id 7D8C537B606 for ; Thu, 13 Jul 2000 12:39:44 -0700 (PDT) (envelope-from joe@ns1.uscreativetypes.com) Received: from localhost (localhost [127.0.0.1]) by ns1.uscreativetypes.com (8.10.0/8.9.3) with ESMTP id e6DJCel33415; Thu, 13 Jul 2000 13:12:44 -0600 (MDT) (envelope-from joe@ns1.uscreativetypes.com) Date: Thu, 13 Jul 2000 13:12:40 -0600 (MDT) From: "Jumpin' Joe Schroedl" X-Sender: joe@localhost To: Brett Glass Cc: Jim King , "David G. Andersen" , security@FreeBSD.ORG Subject: Re: Two kinds of advisories? In-Reply-To: <4.3.2.7.2.20000713132105.04b65f00@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brett: I don't think your problem is the wording in the advisory headers -- I think its with yer people. There are a million things out there which generate panicy and time-wasting calls and emails...I get them every day from teh mundane to the absolutely ludicrous. Your people need to understand that if the word 'ports' shows up in the header, as I believe is now the standard, then it relates to ports. My point is that the headers can be changed again and again, but that only solves a symptom, not the disease. And if the panicy calls keep coming in, there is one solution: bill 'em. If their lack of critical reading skills wastes your time, waste their capital. Sometimes that is the only way :\ Peace all Jumpin Joe Schroedl UCT Digital Designs -------------------- On Thu, 13 Jul 2000, Brett Glass wrote: > At 12:42 PM 7/13/2000, Jim King wrote: > > >Why are they reading the advisories at all if they don't understand them? > > They often aren't. Many are just scanning the headers. Unfortunately, > the headers leave the uninitiated with the wrong impression. I think > that this could be avoided with a slight rephrasing. It would sure save > me a bunch of panicky e-mails and phone calls, which seem to happen no > matter how often I try to educate people. > > --Brett > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message