Re: [Xen-devel] [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT

2017-02-15 Thread Boris Ostrovsky
On 02/13/2017 12:03 PM, Paul Durrant wrote: > The purpose if this ioctl is to allow a user of privcmd to restrict its > operation such that it will no longer service arbitrary hypercalls via > IOCTL_PRIVCMD_HYPERCALL, and will check for a matching domid when > servicing IOCTL_PRIVCMD_DM_OP. The aim

Re: [Xen-devel] [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT

2017-02-13 Thread Boris Ostrovsky
On 02/13/2017 12:03 PM, Paul Durrant wrote: The purpose if this ioctl is to allow a user of privcmd to restrict its operation such that it will no longer service arbitrary hypercalls via IOCTL_PRIVCMD_HYPERCALL, and will check for a matching domid when servicing IOCTL_PRIVCMD_DM_OP. and IOCTL

[Xen-devel] [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT

2017-02-13 Thread Paul Durrant
The purpose if this ioctl is to allow a user of privcmd to restrict its operation such that it will no longer service arbitrary hypercalls via IOCTL_PRIVCMD_HYPERCALL, and will check for a matching domid when servicing IOCTL_PRIVCMD_DM_OP. The aim of this is to limit the attack surface for a compro