From owner-freebsd-security Thu Jul 13 14:59:21 2000 Delivered-To: freebsd-security@freebsd.org Received: from neo.bleeding.com (neo.bleeding.com [209.10.61.250]) by hub.freebsd.org (Postfix) with ESMTP id 8B96E37C778 for ; Thu, 13 Jul 2000 14:59:14 -0700 (PDT) (envelope-from jjwolf@bleeding.com) Received: from localhost (jjwolf@localhost) by neo.bleeding.com (8.9.3/8.9.3) with ESMTP id OAA38562; Thu, 13 Jul 2000 14:59:10 -0700 (PDT) Date: Thu, 13 Jul 2000 14:59:10 -0700 (PDT) From: Justin Wolf To: Garance A Drosihn Cc: security@FreeBSD.ORG Subject: Re: Displacement of Blame[tm] In-Reply-To: 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 > Because we are trying to provide a service to FreeBSD users. Then send it to freebsd-security. Any emails sent to non-FreeBSD lists could still omit the FreeBSD bit from the header. > 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". I thought the advisory had to do with anyone running the version of the software which was included in the ports and had nothing to do with the FreeBSD association. In which case, maybe it would be good to have people read it if they're running the affected version on an OS other than FBSD. > (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) "What's a port?" -Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message