From owner-freebsd-current@FreeBSD.ORG  Sat Oct  8 18:11:15 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 60736106564A;
	Sat,  8 Oct 2011 18:11:15 +0000 (UTC)
	(envelope-from yanegomi@gmail.com)
Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com
	[209.85.216.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 0BF508FC0A;
	Sat,  8 Oct 2011 18:11:14 +0000 (UTC)
Received: by qadz30 with SMTP id z30so4430685qad.13
	for <multiple recipients>; Sat, 08 Oct 2011 11:11:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=PgpKCJsrPF6HcWNGeE/1NWddCDUDfjJPs9yaGZalbE8=;
	b=Q3zpFyPOKxGKb5Z1d3aild6RiQ8hZunE9HapyTXp7TB6JIn74P5tUWqPU7W7cyf6xs
	CkIvoMAP6gT5yopqTfzIswn3p/xb9fdwoJeL0hG7WefEfS1HRQGwoEbCmcInQHCDIQtK
	R498Y/FUDrq90pdclewi5YdGGqsSgNEsHV1DU=
MIME-Version: 1.0
Received: by 10.224.213.10 with SMTP id gu10mr5839789qab.33.1318097474169;
	Sat, 08 Oct 2011 11:11:14 -0700 (PDT)
Received: by 10.224.74.82 with HTTP; Sat, 8 Oct 2011 11:11:13 -0700 (PDT)
In-Reply-To: <CACqU3MWregi9uz9GK5RMic0jxbz6oRj7YwUHnpArdyATWKrxDg@mail.gmail.com>
References: <CACqU3MUQQ6XQTFXhVe1Jtu4Aey3KCdkTcprD7Ojq3oUrdC8b-w@mail.gmail.com>
	<52963.1318092760@critter.freebsd.dk>
	<CACqU3MWregi9uz9GK5RMic0jxbz6oRj7YwUHnpArdyATWKrxDg@mail.gmail.com>
Date: Sat, 8 Oct 2011 11:11:13 -0700
Message-ID: <CAGH67wQx3NDMd9HY0HKizjOPg2k+gQ=bjCaCVmMn1FMQod-ViA@mail.gmail.com>
From: Garrett Cooper <yanegomi@gmail.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Warren Block <wblock@wonkity.com>, Glen Barber <gjb@freebsd.org>,
	Poul-Henning Kamp <phk@phk.freebsd.dk>,
	freebsd-current@freebsd.org, Benjamin Kaduk <kaduk@mit.edu>
Subject: Re: aliasing (or renaming) kern.geom.debugflags
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2011 18:11:15 -0000

On Sat, Oct 8, 2011 at 11:08 AM, Arnaud Lacombe <lacombar@gmail.com> wrote:
> Hi,
>
> On Sat, Oct 8, 2011 at 12:52 PM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
>> In message <CACqU3MUQQ6XQTFXhVe1Jtu4Aey3KCdkTcprD7Ojq3oUrdC8b-w@mail.gmail.com>
>> , Arnaud Lacombe writes:
>>
>>>User do not care to understand the meaning of an option, you leave a
>>>hole somewhere, it will be used. I'm not even speaking about security
>>>issue here...
>>
>> There is a big difference between having an emergency hatch that
>> gives you a chance to escape certain death by running across a
>> shooting range, and on posting a sign telling people to use it as
>> a short-cut.
>>
> I will certainly never ask you to draw blueprints for a shooting
> range. There is NO legitimacy whatsoever for an emergency hatch to
> pass though the firing line.

    Certain groups do use this emergency hatch in production to get
past safeguards and purposely zero out disks. Granted, it's an
ill-advised procedure for most end-users.
Thanks,
-Garrett