All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 5/6] Adding dontaudit for qemu
Date: Sat, 21 Apr 2012 18:12:32 +0200	[thread overview]
Message-ID: <CAPzO=Nx+SrKNu3SDAp_dQn7cfJC3KqukFEbn3HbM63uOWfFz0w@mail.gmail.com> (raw)
In-Reply-To: <4F91C329.1000909@tresys.com>

On Fri, Apr 20, 2012 at 10:12 PM, Christopher J. PeBenito
<cpebenito@tresys.com> wrote:
>> +dontaudit qemu_t self:socket create;
>
> I'm more interesting in finding out what kind of socket this is, so we can create an appropriate object class.

Ok, trying to figure that out now. No luck with just querying though:

Apr 21 17:53:04 hpl kernel: [90637.251881] type=1400
audit(1335023584.573:457): avc:  granted  { create } for  pid=28083
comm="qemu-system-x86" scontext=staff_u:sysadm_r:qemu_t
tcontext=staff_u:sysadm_r:qemu_t tclass=socket

Doesn't give much. An lsof shows:

# lsof -p 28083
qemu-syst 28083 swift    8u     unix 0x0000000000000000         0t0
80203 socket
qemu-syst 28083 swift    9u     unix 0x0000000000000000         0t0
80204 /tmp/vde.28083-00003

but I don't know how to find out more about this socket. It is related
to qemu's VDE networking virtualization (if I drop the "-net
vde,vlan=0" I don't get the attempt to create a socket) but doesn't
seem to be necessary.

/tmp/vde.28083-00003 is of type vde_tmp_t (cfr. patch/RFC regarding
VDE support sent a while ago)

If anyone know of a good resource that I can read on debugging
sockets, I'd love to hear about it.

Wkr,
  Sven Vermeulen

  reply	other threads:[~2012-04-21 16:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 20:02 [refpolicy] [PATCH 0/13] Numerous dontaudits Sven Vermeulen
2012-03-22 20:06 ` [refpolicy] [PATCH 1/13] Adding dontaudit interfaces for files module Sven Vermeulen
2012-04-20 20:10   ` Christopher J. PeBenito
2012-03-22 20:07 ` [refpolicy] [PATCH 2/13] Adding dontaudit on mozilla Sven Vermeulen
2012-04-20 20:12   ` Christopher J. PeBenito
2012-03-22 20:08 ` [refpolicy] [PATCH 3/13] Adding dontaudit on mta Sven Vermeulen
2012-04-20 20:10   ` Christopher J. PeBenito
2012-03-22 20:08 ` [refpolicy] [PATCH 4/13] Adding dontaudits for portage domains Sven Vermeulen
2012-04-20 20:12   ` Christopher J. PeBenito
2012-03-22 20:09 ` [refpolicy] [PATCH 5/6] Adding dontaudit for qemu Sven Vermeulen
2012-04-20 20:12   ` Christopher J. PeBenito
2012-04-21 16:12     ` Sven Vermeulen [this message]
2012-04-23 12:28       ` Christopher J. PeBenito
2012-03-22 20:10 ` [refpolicy] [PATCH 6/13] Adding dontaudit interfaces in sysnet Sven Vermeulen
2012-04-20 20:11   ` Christopher J. PeBenito
2012-03-22 20:10 ` [refpolicy] [PATCH 7/13] Adding dontaudits for xserver Sven Vermeulen
2012-04-20 20:11   ` Christopher J. PeBenito
2012-03-22 20:11 ` [refpolicy] [PATCH 8/13] Do not audit usage of a leaked file descriptor Sven Vermeulen
2012-04-20 20:12   ` Christopher J. PeBenito
2012-03-22 20:12 ` [refpolicy] [PATCH 9/13] Do not audit rw on dhcp client unix_stream_sockets Sven Vermeulen
2012-04-20 20:11   ` Christopher J. PeBenito
2012-03-22 20:12 ` [refpolicy] [PATCH 10/13] Adding dontaudits for mount Sven Vermeulen
2012-04-20 20:12   ` Christopher J. PeBenito
2012-03-22 20:13 ` [refpolicy] [PATCH 11/13] Adding dontaudits for selinuxutil Sven Vermeulen
2012-04-20 20:13   ` Christopher J. PeBenito
2012-03-22 20:13 ` [refpolicy] [PATCH 12/13] Adding dontaudit for sudo Sven Vermeulen
2012-04-20 20:13   ` Christopher J. PeBenito
2012-03-22 20:14 ` [refpolicy] [PATCH 13/13] Adding dontaudits for raid Sven Vermeulen
2012-04-20 20:13   ` Christopher J. PeBenito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPzO=Nx+SrKNu3SDAp_dQn7cfJC3KqukFEbn3HbM63uOWfFz0w@mail.gmail.com' \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.