Felipe Salvador wrote:
On Wed, Aug 30, 2017 at 08:05:18PM +0200, hw wrote:
In this case, no encryption is needed. That is my decision, and if spice thinks
it could make that decision for me, it needs to be fixed.
So I think you can replace
virt-viewer --connect qemu+ssh://<hypervisor_hostname>/system <vm_id>
with[1]
virt-viewer --connect qemu+tcp://example.com/system <vm_id>
[1] http://libvirt.org/drvqemu.html#uris
Thanks! That doesn´t work, either:
(virt-viewer:24879): virt-viewer-DEBUG: connecting ...
(virt-viewer:24879): virt-viewer-DEBUG: Opening connection to libvirt with URI qemu+tcp://vm/system
(virt-viewer:24879): virt-viewer-DEBUG: Error: unable to connect to server at 'vm:16509': Connection refused
I used vnc with a new VM I created yesterday, and that works fine. Seems
like I´ll have to stick with that.
Looking at [1], which mentions complications introduced by security issues,
I´m finding it very questionable why and how it should be a good idea to
connect to what you could call the administration interface of the very thing
that accesses the host with pretty much root privileges and determines and runs
the VMs on a server merely to be able to view what a VM would display on a display
that could be connected to it if it wasn´t a VM.
Isn´t vnc much more secure from that perspective?
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
