Date: Sat, 18 Jun 2011 18:18:44 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: RFC: don't allow any access to unexported mounts for NFSv4 Message-ID: <1829558003.762155.1308435524848.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110618115448.00004b7f@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, 17 Jun 2011 11:41:24 -0400 (EDT) Rick Macklem > <rmacklem@uoguelph.ca> wrote: > > > > The workarounds you propose contradict everything people are used > > > to. They are not easy or you need to care what you put in the > > > parent > > > directories of the one you want to export. It basically means that > > > you can only use NFSv4 on newly setup systems, upgraded or > > > migrated > > > ones look out of the question (yes, I'm over-simplificating a > > > bit). > > > > > > I really hope someone can come up with a fix for this, else it > > > would > > > mean I would not use NFSv4 anywhere. > > > > > Ok, can I assume that's a vote for "leave the hack in"? > > If the pain to let the hack in is not too big: yes, please let it in. > No pain at all. I just wanted to check to see what people thought of it. (I can easily add the Access case for Linux mounts and also a small patch that disallows lookups of regular files. With this, all clients can do is lookup dirs and get their attributes and access info. Neither Read nor Readdir are allowed, so clients must know/guess names.) Thanks for the input, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1829558003.762155.1308435524848.JavaMail.root>