Date: Tue, 17 May 2016 11:58:52 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: "freebsd-fs@FreeBSD.org" <freebsd-fs@freebsd.org> Subject: Re: Bigger MAX_PATH (Was: Re: State of native encryption in ZFS) Message-ID: <9F057D48-5413-437B-A612-64D47E95C846@gmail.com> In-Reply-To: <9ead4b28-9711-5e38-483f-ef9eaf0bc583@digiware.nl> References: <5736E7B4.1000409@gmail.com> <57378707.19425.B54772B@s_sourceforge.nedprod.com> <CAHM0Q_PGvBRbUFOhmin4RKaDKRTRJyjieuaZ5_tjPerK4eRz=w@mail.gmail.com> <57385356.4525.E728971@s_sourceforge.nedprod.com> <9ead4b28-9711-5e38-483f-ef9eaf0bc583@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 15 may 2016 at 12:45, Niall Douglas wrote: >=20 >>> If FreeBSD had a bigger PATH_MAX then stackable encryptions layers >>> like ecryptfs (encfs?) would be viable choices. Because encrypted >>> path components are so long, one runs very rapidly into the maximum >>> path on the system when PATH_MAX is so low. Could you give us some examples where PATH_MAX was too low for you using = ecryptfs ? I (for the moment) do not run into troubles using EncFS. > http://freebsd.1045724.n5.nabble.com/misc-184340-PATH-MAX-not-interope > rable-with-Linux-td5864469.html And examples where PATH_MAX is too low using Rsync ? Is it too low when we want to sync from Linux to FreeBSD ? Or from = FreeBSD to Linux ? Using Rsync over SSH ? Or using the Rsync daemon on the receiving side ? Thank you very much ! Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F057D48-5413-437B-A612-64D47E95C846>