Garrett LeSage

Here's the desktop of CentOS Stream 9 in Cockpit Client (Cockpit's "Desktop" app):  And the same VM connected via SPICE using "Virtual Machine Viewer" (virt-viewer): ![Screenshot...

@BrainwreckedTech: Thanks for the quick reply! I agree with you; you should be able to edit it without having to edit an XML. I think it probably makes the most...

@BrainwreckedTech: It's not a matter of scrolling. The remote display support is intertwined with the functionality of the console. It makes sense for them to be grouped together, not split...

Here's what I was thinking about having the remote options integrated into the console area:  I don't have the edit modal dialog mocked up, but it...

@BrainwreckedTech: Thanks! Those are great suggestions. I've adjusted the console on the Virtual Machine details page:  And moved the remote viewer information in a dialog: ![Remote viewer confirm...

Cockpit Client needs the connection to work over SSH. Perhaps we should have the connection happen through SSH anyway, otherwise the ports won't matter, unless the firewall is bypassed. So...

> You are correct and sticking to SSH to provide an encrypted tunnel is always preferred. Right. We should default to SSH. The gotcha is that it seems the remote...

> Regarding the "skip explanation dialog" proposal, that would not be a domain-related setting but a user-related setting (every user need to see the message once until he installed the...

Thanks again for all the feedback, everyone! Hopefully you'll still be happy to keep sharing your feedback as we work on this more. I've added a ticket internally (to make...

The file handling part of Cockpit Client is being tracked in https://github.com/cockpit-project/cockpit/issues/17626. As Cockpit Client connects through SSH (not using/needing the Cockpit port of 9090), it's all the more important...