On Tue, Feb 07, 2017 at 09:06:55AM +, David Scott wrote:
>
> > On 1 Feb 2017, at 14:49, Juergen Gross wrote:
> >
> > On 27/01/17 12:47, Juergen Gross wrote:
> >> XS_RESTRICT and the xenstore library function xs_restrict() have never
> >> been usable in all configurations
> On 1 Feb 2017, at 14:49, Juergen Gross wrote:
>
> On 27/01/17 12:47, Juergen Gross wrote:
>> XS_RESTRICT and the xenstore library function xs_restrict() have never
>> been usable in all configurations and there are no known users.
>>
>> This functionality was thought to
On 27/01/17 12:47, Juergen Gross wrote:
> XS_RESTRICT and the xenstore library function xs_restrict() have never
> been usable in all configurations and there are no known users.
>
> This functionality was thought to limit access rights of device models
> to xenstore in order to avoid affecting
On Fri, Jan 27, 2017 at 12:47:22PM +0100, Juergen Gross wrote:
> XS_RESTRICT and the xenstore library function xs_restrict() have never
> been usable in all configurations and there are no known users.
>
> This functionality was thought to limit access rights of device models
> to xenstore in
XS_RESTRICT and the xenstore library function xs_restrict() have never
been usable in all configurations and there are no known users.
This functionality was thought to limit access rights of device models
to xenstore in order to avoid affecting other domains in case of a
security breech.