* Daniel P. Berrangé (berra...@redhat.com) wrote: <snip>
> This means QEMU still has to iterate over every single client > on the bus to identify them. If you're doing that, there's > no point in owning a well known service at all. Just iterate > over the unique bus names and look for the exported object > path /org/qemu/VMState > Not knowing anything about DBus security, I want to ask how do we handle security here? I want to know that the external device that's giving me migration data is the device I think I'm speaking to, not one of the other devices; I also dont want different devices chatting to each other over dbus unless we're very careful. Dave > 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 :| -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
