Date: Sun, 6 Dec 2015 17:57:09 -0200 From: =?utf-8?B?THXDrXM=?= Fernando Schultz Xavier da Silveira <schultz@ime.usp.br> To: Anton Sayetsky <vsasjason@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: OSS in jail Message-ID: <20151206195709.GA4100@hpmini> In-Reply-To: <CAA2O=b_o=Jfmg=ny6JDvgeznR_HVpBr%2BBO0anPFDfsUBp_RBKQ@mail.gmail.com> References: <20151206194401.GA3860@hpmini> <CAA2O=b_isQOHepigMgDyDGtOidpbYkLOmvEayCbETfLEbUsDKA@mail.gmail.com> <20151206194851.GA4044@hpmini> <CAA2O=b_o=Jfmg=ny6JDvgeznR_HVpBr%2BBO0anPFDfsUBp_RBKQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Pleas, reply to list instead of users. Sorry. > If a user has write access, how do you want to prevent him to set permissions? This is the precise problem. I need either a stronger form of access control than unix permissions or two separate devices for playback and recording. Or maybe a separate OSS stack, in the spirit of VIMAGE. These options seem unrealistic, but the use case does not seem unreasonable, which is why I pose the question.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151206195709.GA4100>