[libvirt] [PATCH] AppArmor: allow QEMU to set_process_name.

Jamie Strandboge jamie at canonical.com
Wed Dec 7 14:53:17 UTC 2016

On Wed, 2016-12-07 at 08:37 +0100, Christian Ehrhardt wrote:
> On Tue, Dec 6, 2016 at 5:40 PM, Jamie Strandboge <jamie at canonical.com>
> wrote:
> > 
> > I forgot to reiterate: the above is true *unless* there is another
> > non-DAC, non-
> > MAC kernel mediation (eg, does the kernel only allow modifying the 'comm'
> > value
> > of its own threads? If so, then the rule would be safe to add to the
> > default
> > abstraction (though we should document that it is safe)).
> > 
> Thanks for your help Jamie on thinking through the implications of this - I
> really highly appreciate!
> For the given interface the v2 should be safe see e.g.
> http://man7.org/linux/man-pages/man5/proc.5.html
> Quoting from there: "... A thread may modify *its* comm value, or that of
> any of other thread *in the same thread group* ..."

Thanks for investigating this. +1 on adding this it the libvirt-qemu

# Per man(5) proc, the kernel enforces that a thread may
# only modify its comm value or those in its thread group.
owner @{PROC}/@{pid}/task/@{tid}/comm rw,

Jamie Strandboge             | http://www.canonical.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20161207/3ad5d1a3/attachment-0001.sig>

More information about the libvir-list mailing list