search for: deplyoment

Hi there everyone, I have a rails app that used Google Maps in some of the views. In order to use it I have to include the following code at the top of my view: <script src="http://maps.google.com/maps?file=api&amp;v=2&amp;key=ABQIAAAAIMKpaY7H31fBaN42JFh17RTJQa0g3IQ9GZqIMmInSLzwtGDKaBR7f3BOyzEp9wqLchJrd7-MYS2n0Q" type="text/javascript"></script> However,

...manner, or you will have to turn off > SELinux support in libvirtd. in /etc/libvirt/qemu.conf via the > param security_driver = "none". If you turn off SELinux in > libvirt, then you no longer have separation of QEMU processes > which may be a security flaw depending on your deplyoment > scenario. > turning SELinux in libvirtd off or allowing libvirt to relabel are tempting options but it is not an option I'm afraid due to security concerns. Our plan (or at least this particular effort) is to try to relabel the tun-socket after created in the super-privileged container...

Hello all, tl;dr, can you point me to the point in the libvirt repo where it's trying to change a tap-device's SELinux label? I am trying to create a tap device with libvirt on a super-privileged container, and then use it on another, unprivileged container with libvirt. User wise, I know I need the super-privileged container to open the tap device with the user of the unprivileged one -

...stuff in the normal manner, or you will have to turn off SELinux support in libvirtd. in /etc/libvirt/qemu.conf via the param security_driver = "none". If you turn off SELinux in libvirt, then you no longer have separation of QEMU processes which may be a security flaw depending on your deplyoment scenario. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

...have to turn off > > SELinux support in libvirtd. in /etc/libvirt/qemu.conf via the > > param security_driver = "none". If you turn off SELinux in > > libvirt, then you no longer have separation of QEMU processes > > which may be a security flaw depending on your deplyoment > > scenario. > > > turning SELinux in libvirtd off or allowing libvirt to relabel are tempting > options but it is not an option I'm afraid due to security concerns. > Our plan (or at least this particular effort) is to try to relabel the > tun-socket after created in t...

...; > > SELinux support in libvirtd. in /etc/libvirt/qemu.conf via the > > > param security_driver = "none". If you turn off SELinux in > > > libvirt, then you no longer have separation of QEMU processes > > > which may be a security flaw depending on your deplyoment > > > scenario. > > > > > turning SELinux in libvirtd off or allowing libvirt to relabel are > tempting > > options but it is not an option I'm afraid due to security concerns. > > Our plan (or at least this particular effort) is to try to relabel the >...