From owner-freebsd-jail@freebsd.org  Mon Dec 12 23:04:00 2016
Return-Path: <owner-freebsd-jail@freebsd.org>
Delivered-To: freebsd-jail@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8CD5C74D1E
 for <freebsd-jail@mailman.ysv.freebsd.org>;
 Mon, 12 Dec 2016 23:04:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D820BEDC
 for <freebsd-jail@FreeBSD.org>; Mon, 12 Dec 2016 23:04:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBCN40xN095333
 for <freebsd-jail@FreeBSD.org>; Mon, 12 Dec 2016 23:04:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-jail@FreeBSD.org
Subject: [Bug 215250] jail break under particular circumstance
Date: Mon, 12 Dec 2016 23:04:01 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: simonp@email.it
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Works As Intended
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-jail@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-215250-9824-mfrEfvz1n5@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215250-9824@https.bugs.freebsd.org/bugzilla/>
References: <bug-215250-9824@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-jail@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion about FreeBSD jail\(8\)" <freebsd-jail.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-jail/>
List-Post: <mailto:freebsd-jail@freebsd.org>
List-Help: <mailto:freebsd-jail-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2016 23:04:01 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215250

--- Comment #3 from simonp@email.it ---
(In reply to Jamie Gritton from comment #2)

Thank you very much you guys,

As pointed by myself the case is absolutely particular,
and indeed you have no need to "break" a jail=20
if you have admin permission for the host system ;-) ...

However some unaware sysadm, or a buggy script may lead
to the situation described, so, better to have had look ...=20
thank you again

--=20
You are receiving this mail because:
You are the assignee for the bug.=