From owner-freebsd-questions@FreeBSD.ORG Mon Apr 2 10:12:59 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6CB11065670 for ; Mon, 2 Apr 2012 10:12:59 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 403538FC0A for ; Mon, 2 Apr 2012 10:12:59 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.182]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id B47255C22 for ; Mon, 2 Apr 2012 20:26:33 +1000 (EST) Message-ID: <4F797BA9.6010204@herveybayaustralia.com.au> Date: Mon, 02 Apr 2012 20:12:57 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20120401045919.246CE1065672@hub.freebsd.org> <20120402163942.K2060@sola.nimnet.asn.au> In-Reply-To: <20120402163942.K2060@sola.nimnet.asn.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD Security in Multiuser Environments X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2012 10:12:59 -0000 On 04/02/12 17:48, Ian Smith wrote: > In freebsd-questions Digest, Vol 408, Issue 10, Message: 5 > On Sat, 31 Mar 2012 21:05:00 +0700 Erich Dollansky wrote: > > On Saturday 31 March 2012 20:26:14 Julian H. Stacey wrote: > [..] > > > Da Rock wrote: > > > > On 03/31/12 17:46, Julian H. Stacey wrote: > [..] > > > > > schultz@ime.usp.br wrote: > > > > >> Hello, > > > > >> > > > > >> I would like to raise a discussion about the security features > > > > >> of FreeBSD as a whole and how they might be employed to actually > > > > >> derive some meaningful guarantees. > > > > > > We have a list specialy for freebsd-security@. Please use it. > > I thought this to be sensible advice. Before seeing that I'd thought of > copying it to rwatson@ who I figured might take an interest due to his > involvement with Capsicum, acl(3) and such, but he certainly reads that > list anyway (and more than likely, not this one :) > > > > > Hang on, hold the phone: The security list (specifically) is for > > > > security announcements. At least that what it said when I subscribed to > > > > it... > > > > > > Wrong. > > Correct :) So thats turn left, right? Clear as mud now... :) > > > > For list of mail lists see: > > > http://lists.freebsd.org/mailman/listinfo > > > > > > Specifically: > > > freebsd-security@freebsd.org > > > http://lists.freebsd.org/mailman/listinfo/freebsd-security > > > > > > freebsd-security-notifications@freebsd.org > > > http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications > > > this sounds very confusing for people who have simple question: > > > > 'General system administrator questions of an FAQ nature are > > off-topic for this list, but the creation and maintenance of a FAQ is > > on-topic. Thus, the submission of questions (with answers) for > > inclusion into the FAQ is welcome. Such question/answer sets should > > be clearly marked as (at least "FAQ submission") such in the subject. > > ' > > schultz' post was nothing in the way of an FAQ issue, but a request for > discussion of a wide range of system security issues, far indeed from a > 'simple question'. Had you posted the two paragraphs before the one you > quote above, this may have been a little clearer. To wit: > > "This is a technical discussion list covering FreeBSD security issues. > The intention is for the list to contain a high-signal, low-noise > discussion of issues affecting the security of FreeBSD. I think that has clarified things sufficiently now. Looks like I should subscribe to that list too.