From owner-freebsd-security Thu Jul 13 13:12:22 2000 Delivered-To: freebsd-security@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 5051E37B531 for ; Thu, 13 Jul 2000 13:12:18 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA328170; Thu, 13 Jul 2000 16:11:54 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <4.3.1.2.20000713140640.00dcdcd0@mail.voltage.net> References: <200007131814.MAA22497@faith.cs.utah.edu> <4.3.2.7.2.20000713120631.04d53b60@localhost> <4.3.1.2.20000713140640.00dcdcd0@mail.voltage.net> Date: Thu, 13 Jul 2000 16:12:56 -0400 To: Susie Ward , Brett Glass From: Garance A Drosihn Subject: Re: Two kinds of advisories? Cc: security@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 2:08 PM -0500 7/13/00, Susie Ward wrote: >At 12:26 PM 7/13/00 -0600, Brett Glass wrote: >>Many of them don't read the disclaimers because they're scanning >>the subject lines. When they see one with "FreeBSD" in it, some >>of them call in a panic. They often don't read the message because >>they believe that they won't understand it. > >If they don't understand it, then maybe you shouldn't be encouraging >them to join bugtraq, but I am curious what you'd like to see the >subject lines say? Instead of "FreeBSD Ports Security Advisory: " Perhaps: "Ports for FreeBSD Security Advisory: " I am not sure that is much of an improvement, but I can see the basic point that Brett is concerned about here. I don't know if there is any good solution, because a really unambiguous description would probably be too long for a 1-line subject... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message