All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Paris <eparis@redhat.com>,
	Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC] Continuous work on sandboxing
Date: Mon, 29 Apr 2013 17:52:10 -0400	[thread overview]
Message-ID: <517EEB8A.7040700@linux.vnet.ibm.com> (raw)
In-Reply-To: <7515044.dYPbKXmJQB@sifl>



On 04/26/2013 05:07 PM, Paul Moore wrote:
> [snip]
>
>> >3. Debugging and/or learning mode - third party libraries still have the
>> >problem of interfering in the Qemu's signal mask. According to some
>> >previous discussions, perhaps patch all external libraries that mass up
>> >with this mask (spice, for example) is a way to solve it. But not sure
>> >if it worth the time spent. Would like to hear you guys.
> I think patching all the libraries is a losing battle, I think we need to
> pursue alternate debugging techniques.
>
> -- paul moore security and virtualization @ redhat
>

I agree.  It would be nice to have some sort of learning mode that 
reported all denied syscalls on a single run, but signal handlers 
doesn't seem like the right way.  Maybe we could improve on this 
approach, since it never gained traction: https://lkml.org/lkml/2013/1/7/313

At least we can get a single denied syscall at a time today via the 
audit log that the kernel issues.  Eduardo, you may want to see if 
there's a good place to document that for QEMU so that people know where 
to look.

-- 
Regards,
Corey Bryant

  parent reply	other threads:[~2013-04-29 21:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 18:39 [Qemu-devel] [RFC] Continuous work on sandboxing Eduardo Otubo
2013-04-26 21:07 ` Paul Moore
2013-04-26 22:17   ` Paolo Bonzini
2013-04-29 19:57     ` Eduardo Otubo
2013-04-29 21:06       ` Paolo Bonzini
2013-04-29 18:39   ` Eduardo Otubo
2013-04-29 19:24     ` Paul Moore
2013-04-29 22:02     ` Corey Bryant
2013-04-30 18:47       ` Eduardo Otubo
2013-04-30 20:28         ` Corey Bryant
2013-05-01 14:13           ` Paul Moore
2013-05-01 15:30             ` Corey Bryant
2013-04-29 21:52   ` Corey Bryant [this message]
2013-04-30 15:24     ` Paul Moore
2013-05-01 17:25       ` Eduardo Otubo
2013-05-01 18:04         ` Corey Bryant

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=517EEB8A.7040700@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=eparis@redhat.com \
    --cc=otubo@linux.vnet.ibm.com \
    --cc=pmoore@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.