From owner-freebsd-fs@freebsd.org Wed Aug 22 03:11:56 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3F831089901; Wed, 22 Aug 2018 03:11:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5043B7D525; Wed, 22 Aug 2018 03:11:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f180.google.com with SMTP id 203-v6so324178ljj.13; Tue, 21 Aug 2018 20:11:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2H77byjIsdHOagXX3E6B0cd9+5m33eRiPqKcdQc6duw=; b=ndDZAcx+HhcvU9zVPa85IMDB3edx9YJZLID8PZtK4pK63MO0G1a2ipFR1jAlDEB5CU aNErPir4NI3GuabzUXa22pP4E7BT+Jdrir2s963CeZJxNOscpZvaTPzcEUnmbHJGxm+3 E3VZAbY0ELMctQPUpEvo5wXa3LexogUAv46AKqqHh+Bsd7/Eqibrzaqn8u9Uoyz3Mxyn GChFn/C6+3yMrlpfCpvrkl1v1g8WfSirtX4ztPWrF42C1QiTkcIsRYoXE6bPZ9di29K/ D5cTDgBrpY+pfl/Y01BLtoK2LJuWuRB3Cng0vx/kSVSnvaZLy++Bavb3sPhylZHTp+I6 wogA== X-Gm-Message-State: AOUpUlHsx0lfic7T9mPQH94C7K74MW5A1omgTznXje0eJApRFQszsVR3 wtoePnSZ0q+ithSgAYwaUaomiIrVyetB0VdNT0VITQ== X-Google-Smtp-Source: AA+uWPwQXwYR0S7XM4YwMSO84aJc973FVyCEVHcJdMreNfRTJihx1IJYHV+i+cGYjX7k5+OsXjY6wDMrl0Oyw4emo8A= X-Received: by 2002:a2e:2067:: with SMTP id g100-v6mr35044269ljg.138.1534907507989; Tue, 21 Aug 2018 20:11:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Tue, 21 Aug 2018 21:11:36 -0600 Message-ID: Subject: Re: Native Encryption for ZFS on FreeBSD CFT To: Matthew Macy Cc: FreeBSD CURRENT , freebsd-fs , Sean Fagan Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2018 03:11:56 -0000 The last time I looked (which was a long time ago), Oracle's ZFS encryption looked extremely vulnerable to watermarking attacks. Did anybody ever fix that? -Alan On Tue, Aug 21, 2018 at 8:28 PM Matthew Macy wrote: > On Tue, Aug 21, 2018 at 6:55 PM Matthew Macy wrote: > > > To anyone with an interest in native encryption in ZFS please test the > > projects/zfs-crypto-merge-0820 branch in my freebsd repo: > > https://github.com/mattmacy/networking.git > > > > > Oh and I neglected to state that this work is being supported by iX Systems > and the tree is all built on work done by Sean Fagan at iX Systems. Please > keep him in the loop on any problems encountered. > Thanks. > > > > > ( git clone https://github.com/mattmacy/networking.git -b > > projects/zfs-crypto-merge-0820 ) > > > > The UI is quite close to the Oracle Solaris ZFS crypto with minor > > differences for specifying key location. > > > > Please note that once a feature is enabled on a pool it can't be > > disabled. This means that if you enable encryption support on a pool > > you will never be able to import it in to a ZFS without encryption > > support. For this reason I would strongly advise against using this on > > any pool that can't be easily replaced until this change has made its > > way in to HEAD after the freeze has been lifted. > > > > > > By way of background the original ZoL commit can be found at: > > > > > https://github.com/zfsonlinux/zfs/pull/5769/commits/5aef9bedc801830264428c64cd2242d1b786fd49 > > > > Thanks in advance. > > -M > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >