From owner-freebsd-fs@freebsd.org Tue May 15 11:07:14 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 31538EADD7C for ; Tue, 15 May 2018 11:07:14 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Received: from mail.yellowspace.net (mail.yellowspace.net [62.146.62.104]) by mx1.freebsd.org (Postfix) with ESMTP id C7A026CA1A for ; Tue, 15 May 2018 11:07:13 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Received: from furia.intranet ([212.114.226.80]) (AUTH: PLAIN lopez.on.the.lists@yellowspace.net, SSL: TLSv1/SSLv3, 128bits, AES128-SHA) by mail.yellowspace.net with esmtp; Tue, 15 May 2018 13:02:06 +0200 id 000147E9.000000005AFABE2E.0000A672 Subject: Re: Native ZFS encryption To: freebsd-fs@freebsd.org References: <3e0b2644-9739-5341-0295-c746275588ec@aon.at> <0bf3fd08-1803-e15b-cadf-755d1c0af325@multiplay.co.uk> From: Lorenzo Perone Message-ID: Date: Tue, 15 May 2018 13:02:05 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <0bf3fd08-1803-e15b-cadf-755d1c0af325@multiplay.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 11:07:14 -0000 Hi, does anyone know whether there is an update on this, FreeBSD-wise, or if it is planned? It looks like the new pull request for openzfs, https://github.com/openzfs/openzfs/pull/489 has come a few steps further. I've also seen the dataset/zvol encryption functionality "sort of working" on one of the latest OpenZFS on OS X version (1.7.3 Beta). Being able to have encryption at the dataset/zvol level is, imo, a very nice option: It allows to share the space and hardware redundancy between different users, while keeping their data encrypted with separate keys - as opposed to the (very well working) "GELI below" option. On the more general matter, I wondered if anyone has a pointer to any documentation / article / comment (other than the code itself) on how "compatible" the openzfs and FreeBSD-zfs implementations actually are? I wonder for example how FreeBSD specific features like "zfs jail" are kept while/if merging code from openzfs? (as a side note: another FreeBSD specific feature being, of course, longterm-proven reliability..) Best Regards to all active developers, Lorenzo On 04.01.17 18:32, Steven Hartland wrote: > Typically once its merged upstream (openzfs) after then it will get > pulled in. > > Status of that request is currently conflicting: > https://github.com/openzfs/openzfs/pull/124 > > On 04/01/2017 15:15, Martin Birgmeier wrote: >> Tom Caputi is working on Native ZFS encryption for Linux: >> https://github.com/zfsonlinux/zfs/pull/4329 >> >> What are the plans/what is the status for incorporating this into >> FreeBSD? >> >> -- Martin >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"