Re: [libvirt] [dbus PATCH 4/8] Implement Encrypted property for Connect Interface
On Mon, Apr 09, 2018 at 02:40:27PM +0200, Pavel Hrdina wrote:
On Mon, Apr 09, 2018 at 01:47:35PM +0200, Katerina Koukiou wrote:
> Signed-off-by: Katerina Koukiou <kkoukiou(a)redhat.com>
> ---
> data/org.libvirt.Connect.xml | 4 ++++
> src/connect.c | 20 ++++++++++++++++++++
> test/test_connect.py | 1 +
> 3 files changed, 25 insertions(+)
This and the Secure properties are not that simple to just export
them. The reason is that the communication over D-Bus can be monitored
even if the connection from libvirt-dbus to libvirt is secure. I would
skip these two properties for now until we figure it out.
I don't think that's a big problem - I think it is just a documentation
task to say that monitoring of traffic on the dbus message bus is out
of scope for these properties. IOW they just reflect the security
properties of the libvirt-dbus <-> hypervisor paths, not the
dbus client <-> hypervisor paths
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 :|