From owner-freebsd-fs@freebsd.org Wed Sep 20 21:01:31 2017 Return-Path: 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 525D2E233CB for ; Wed, 20 Sep 2017 21:01: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 401AD7F732 for ; Wed, 20 Sep 2017 21:01: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 v8KL1Uuk029269 for ; Wed, 20 Sep 2017 21:01: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:01:30 +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: vlad-fbsd@acheronmedia.com 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: Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 21:01:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214981 --- Comment #4 from Vladimir Krstulja --- (In reply to Andriy Gapon from comment #3) Unfortunately, in my view, that doesn't change anything. One major problem = is with ZFS receives, which is what hit me in this case. The server was receiv= ing backup pools from production, a root pool included. The obvious part is solved with import -R or -N, and giving -u to `zfs rece= ive` so it doesn't mount received snapshots. All was well until after quite a lo= ng time I had to reboot the server. The act of unlocking the drives that conta= ined the backup datasets, the very act of hitting enter on last geli passphrase imported and mounted everything it found, so I haven't had a chance to -R or -N. The security problem in this is also through received datasets. One could a= rgue that you have to trust data you receive, and I partially agree. It doesn't = help that ZFS does not, with this, offer any safety net in an form of an ability= to prevent automatic importing + mounting, from happening at all. Oh yeah, dis= able zfs service maybe. But totally not a solution. Automatic, implicit, quiet, non-obvious remounts, especially of /, without = the user explicitly stating it's okay to do so, should NEVER happen. Ever. I really hope this issue will be treated as a serious problem. --=20 You are receiving this mail because: You are the assignee for the bug.=