From owner-freebsd-fs@freebsd.org  Wed Sep 20 21:32:31 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 D768AE24DAA
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 20 Sep 2017 21:32:31 +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 C5AEF8113D
 for <freebsd-fs@FreeBSD.org>; Wed, 20 Sep 2017 21:32:31 +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 v8KLWV7a007476
 for <freebsd-fs@FreeBSD.org>; Wed, 20 Sep 2017 21:32:31 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 214981] ZFS happily and silently remounts any existing mount on
 pool import (POLA violation and security issue!)
Date: Wed, 20 Sep 2017 21:32:31 +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-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: smh@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-214981-3630-RKAsz4V4la@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214981-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-214981-3630@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-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 21:32:32 -0000

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

Steven Hartland <smh@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |smh@FreeBSD.org

--- Comment #5 from Steven Hartland <smh@FreeBSD.org> ---
I think the option your looking for is the canmount property.

At the end of the day there are loads of ways to break things from rm -rf or
zfs destroy to pulling out a physical disk.

ZFS is a very powerful tool and it rightly assumes you know what your doing=
.=20

Ensuring you=E2=80=99re aware of how receiving streams work and that unless=
 told
otherwise you want the file systems mounted is just part of your responsibi=
lity
when you have that power.

Have I shot myself in the foot by receiving a stream without disabling moun=
t,
yes I have, do I believe ZFS should have prevented me from doing something =
so
stupid absolutely not.

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