On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
> I'm working on a completely refactoring of the seccomp feature in qemu:
> https://github.com/otubo/qemu/commits/seccomp-refactoring

Nice. Since you are moving from whitelisting to blacklisting I don't
think that will be easy to backport/SRU but I'll leave it up to you.

> These patches are intended to 2.9, but will be able to be backported.
> What's the urgency of this issue? Do you need a hotfix for it directly
> for 2.5 or can wait until my refactoring hits 2.9?

There is no rush since we've been waiting since Trusty/2.0 already :)
We'll start our new Xenial/2.5 cluster without sandbox and we'll revisit
this once a SRU lands in Xenial. Please don't hesitate to ask me to test
something if that can help. Thanks for the prompt reply!

Regards,
Simon

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675114

Title:
  QEMU seccomp sandbox missing a whitelist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1675114/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to