Date: Thu, 13 Jul 2000 17:44:47 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Justin Wolf <jjwolf@bleeding.com>, security@FreeBSD.ORG Subject: Re: Displacement of Blame[tm] Message-ID: <v04210103b593e68bacc5@[128.113.24.47]> In-Reply-To: <Pine.BSF.4.21.0007131337260.38269-100000@neo.bleeding.com> References: <Pine.BSF.4.21.0007131337260.38269-100000@neo.bleeding.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:44 PM -0700 7/13/00, Justin Wolf wrote: >Maybe I missed it in this really long thread somewhere, but >why do we have to say that it concerns FreeBSD at all? Because we are trying to provide a service to FreeBSD users. If there is NO mention of freebsd, then they will either ignore it completely, or they will send messages to this (freebsd) mailing list saying "Does security advisory X apply to FreeBSD?". So we want some mention of freebsd, but it would be nice if we could come up with a subject-format which didn't make it so easy to assume the advisory is for the core freebsd operating system. In my case, I am thinking how these subjects look to people are NOT currently running freebsd, and thus they have absolutely no reason to read the whole article to "learn" the distinction between "FreeBSD" and "FreeBSD Ports". Note that this means my concern isn't exactly the same as Brett's original message, but it is mighty similar. (also note that I do think that the recent addition of the word "Ports" to the subject line may be enough to address these concerns) --- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04210103b593e68bacc5>