Date: Thu, 7 Nov 2019 03:36:22 +0100 From: Jan Behrens <jbe-mlist@magnetkern.de> To: freebsd-fs@freebsd.org Subject: Re: ZFS snapdir readability (Crosspost) Message-ID: <20191107033622.16414272ae743d50f75786ec@magnetkern.de> In-Reply-To: <0a823048-d191-72e8-e20b-0491ebd4ea4a@peak.org> References: <20191107004635.c6d2e7d464d3d556a0d87465@magnetkern.de> <CAOtMX2huHZcXHH%2B=3Bx7hX_p9udJ2acOX%2BZL8vW=pjqbe6mOAA@mail.gmail.com> <20191107012027.9639f3a9dda1941518358a52@magnetkern.de> <0a823048-d191-72e8-e20b-0491ebd4ea4a@peak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 6 Nov 2019 16:36:08 -0800 Alan Batie <alan@peak.org> wrote: > On 11/6/19 4:20 PM, Jan Behrens wrote: > > > My problem here is that with most (or maybe even all) other backup > > systems, I would be able to restrict ordinary users from accessing all > > backups. So I consider this problem to be pretty much unique to ZFS > > This is going to be a problem with any system that does snapshots - our > Netapps would also have the same issue, and it's unfortunate, but one > you want as you want users to be able to recover their files on their > own, it's part of the point... I understand the point now. Not all application fields of snapshots, however, (whether backup or replication or other) have the purpose of letting non-privileged users access the data. With the current implementation of ZFS I have no choice on whether I want this behavior or consider it a security problem that should be avoided in my scenario. This also applies to snapshots taken for other reasons than (user readable) backups. Regards, Jan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191107033622.16414272ae743d50f75786ec>