Re: [libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-03-06 Thread Michal Privoznik
On 06.03.2017 12:43, Peter Krempa wrote: > On Tue, Feb 14, 2017 at 15:30:44 +0100, Michal Privoznik wrote: >> Now that we have some qemuSecurity wrappers over >> virSecurityManager APIs, lets make sure everybody sticks with >> them. We have them for a reason and calling virSecurityManager >> API

Re: [libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-03-06 Thread Peter Krempa
On Tue, Feb 14, 2017 at 15:30:44 +0100, Michal Privoznik wrote: > Now that we have some qemuSecurity wrappers over > virSecurityManager APIs, lets make sure everybody sticks with > them. We have them for a reason and calling virSecurityManager > API directly instead of wrapper may lead into

Re: [libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-02-20 Thread Michal Privoznik
On 20.02.2017 12:55, Daniel P. Berrange wrote: > On Mon, Feb 20, 2017 at 12:50:23PM +0100, Peter Krempa wrote: >> On Tue, Feb 14, 2017 at 15:30:44 +0100, Michal Privoznik wrote: >>> Now that we have some qemuSecurity wrappers over >>> virSecurityManager APIs, lets make sure everybody sticks with

Re: [libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-02-20 Thread Martin Kletzander
On Mon, Feb 20, 2017 at 11:55:06AM +, Daniel P. Berrange wrote: On Mon, Feb 20, 2017 at 12:50:23PM +0100, Peter Krempa wrote: On Tue, Feb 14, 2017 at 15:30:44 +0100, Michal Privoznik wrote: > Now that we have some qemuSecurity wrappers over > virSecurityManager APIs, lets make sure

Re: [libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-02-20 Thread Daniel P. Berrange
On Mon, Feb 20, 2017 at 12:50:23PM +0100, Peter Krempa wrote: > On Tue, Feb 14, 2017 at 15:30:44 +0100, Michal Privoznik wrote: > > Now that we have some qemuSecurity wrappers over > > virSecurityManager APIs, lets make sure everybody sticks with > > them. We have them for a reason and calling

Re: [libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-02-20 Thread Peter Krempa
On Tue, Feb 14, 2017 at 15:30:44 +0100, Michal Privoznik wrote: > Now that we have some qemuSecurity wrappers over > virSecurityManager APIs, lets make sure everybody sticks with > them. We have them for a reason and calling virSecurityManager > API directly instead of wrapper may lead into

[libvirt] [PATCH] qemu: Enforce qemuSecurity wrappers

2017-02-14 Thread Michal Privoznik
Now that we have some qemuSecurity wrappers over virSecurityManager APIs, lets make sure everybody sticks with them. We have them for a reason and calling virSecurityManager API directly instead of wrapper may lead into accidentally labelling a file on the host instead of namespace.