Saturday, 2017-02-25

tristanCmordred: clarkb: jeblair: well bubblewrap is specifically designed to be "safely" used by unpriviledge user... what are the problems you are trying to fix with it?00:38
SpamapStristanC: we want to run ansible-playbook in a sandbox where it can't inspect or affect things on the host running it.00:43
SpamapSso, chroot++00:43
*** gk_-1wm_- has joined #zuul01:18
*** gk_-1wm_- has left #zuul01:18
tristanCSpamapS: filesystem/ipc wise, bwrap can easily isolate an ansible-playbook process, here is a little experiment: http://paste.openstack.org/show/600431/01:23
tristanCthough, further network isolation would need more work, not provided by bwrap afaik01:27
SpamapStristanC: actual network access can be handled by normal egress firewalling and user separation I think. But we don't want them to be able to read the system configuration like say, 'ip route' would.01:44
tristanCSpamapS: I meant network namespace, bwrap can create them, but it doesn't seems to setup, like create the veth and virtual routes01:49
SpamapStristanC: Oh, yeah I don't think I'd want it to.01:51
SpamapSthat would mean I'd have to plumb that network namespace out to the target machines.01:51
SpamapSthough I guess that's the way to do what I ultimately want and hide the details01:52
* SpamapS notes this is getting a little dockery01:52
tristanCSpamapS: not necessarly down to the target machines, it's actually trivial to create a local virtual network so that the sandbox process can't inspect host interfaces or routes02:00
SpamapStristanC: ah, so just shove a veth into the namespace or something?02:02
SpamapSthat would be ideal really02:02
tristanCSpamapS: yes, but this requires additional privileges... at that point, it's probably better to rely on a fully fledge container framework instead of giving extra powers to the parent process02:05
SpamapStristanC: yeah, I keep falling back to "let's start with lxc and see if that gets us there"02:14
SpamapSand maybe wrap it in a little selinux/apparmor too02:15
* SpamapS weekends02:15
*** bstinson has quit IRC02:26
*** bstinson has joined #zuul02:26
tristanCif it's acceptable to give zuul process such access, then I would recommend runC since it's more flexible :)02:35
*** gk__1wm_ has joined #zuul04:04
*** gk__1wm_ has left #zuul04:04
*** gk-----------1wm has joined #zuul04:12
*** gk-----------1wm has quit IRC04:13
*** IRCFrEAK has joined #zuul04:23
*** IRCFrEAK has quit IRC04:25
mordredSpamapS, tristanC: yah - so, I don't think we're as concerned about networks as we are with filesystems. which is to say - given the choice between being able to run without elevated privs and no network separation, or getting network separation but needing zuul to get root access, I believe we'd prefer to not have network separation04:32
mordredone of the reasons to get to bubblewrap is the fact that runC and lxc _do_ require the calling process to have root04:33
mordredof course, this is all a set of tradeoffs and balances04:33
mordredso we may also want to lay out a comparison of what we get with each approach and what the cost is04:33
*** gk_-__-1wm has joined #zuul04:43
*** gk_-__-1wm has quit IRC04:44
*** GK[]\`_^{|}1WM has joined #zuul05:00
*** GK[]\`_^{|}1WM has quit IRC05:08
*** rbergero1 has joined #zuul05:14
*** GK[]\`_^{|}1WM has joined #zuul05:15
*** GK[]\`_^{|}1WM has left #zuul05:15
*** rbergeron has quit IRC05:16
*** EmilienM has quit IRC05:16
*** EmilienM has joined #zuul05:20
*** EmilienM has quit IRC05:41
*** EmilienM has joined #zuul05:44
*** persia has quit IRC07:01
*** persia has joined #zuul07:06
*** saneax-_-|AFK is now known as saneax07:22
*** saneax is now known as saneax-_-|AFK07:34
*** saneax-_-|AFK is now known as saneax10:05
*** saneax is now known as saneax-_-|AFK10:35
*** mgagne has quit IRC11:35
*** mgagne has joined #zuul11:36
*** mgagne is now known as Guest555111:36
*** Cibo_ has joined #zuul12:20
*** Cibo_ has quit IRC12:29
*** Cibo_ has joined #zuul12:32
*** Cibo_ has quit IRC12:36
*** rbergero1 is now known as rbergero17:30
*** rbergero is now known as rbergeron17:30
*** rbergeron has quit IRC17:30
*** rbergeron has joined #zuul17:30
*** yolanda has joined #zuul17:49
*** yolanda has quit IRC17:51
*** yolanda has joined #zuul18:14
*** yolanda has quit IRC18:17
*** yolanda has joined #zuul20:25

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!