search

QubesOS / qubes-issues

The Qubes OS Project issue tracker
https://www.qubes-os.org/doc/issue-tracking/
526 stars 46 forks source link

For dispVMs, also include the source VM name, if applicable, between the dispVM name and the VM-supplied window title. #4781

Open brendanhoar opened 5 years ago

brendanhoar commented 5 years ago

Qubes OS version:

R4.0.1

Affected component(s):

Qubes Window Titles

Steps to reproduce the behavior:

Open any application window in a VM

Expected behavior:

See color of VM, calculated dispVM name in brackets, source VM name in brackets and in-VM actual window title all concatenated.

Actual behavior:

See color of VM, calculated dispVM name in brackets, and in-VM actual window title all concatenated. No indication of the AppVM that sourced this dispVM.

General notes:

For those who utilize disposable VMs with multiple VPNs or other proxies, one way in which the user can better enforce separation of connections (i.e. to perhaps de-correlate data access patterns or personas) is to set up multiple several network-providing VMs with different configurations and the same number of app VMs (possibly for use as dispVMs) which are configured one-to-one with these network-providing VMs.

This works OK when not using dispVMs since you can name the AppVMs appropiately and it is clear at a glance which AppVMs are using which NetVMs.

However, when using dispVMs this becomes more tricky. One could fall back onto using the VM labels and correlate the colors between the AppVM and network-providing VMs, but that does not seem optimal.

Instead, I would prefer to see name of the source AppVM for the dispVM included as part of the window title (after the disp##### designation). This would lead to less possibilities of errors in data access or persona cross-contamination.

Related issues:

SaswatPadhi commented 4 years ago

I just faced this issue as well. My DispVMs had the same color and I had no way of knowing which one was based on which source VM.

I even looked at the qubesdb keys and I couldn't find any key that could tell me the template name or something. While this feature is pending, is there any temporary workaround for this?

Thanks.

airelemental commented 4 years ago

While this feature is pending, is there any temporary workaround for this?

qvm-prefs disp1841 template shows the source VM for me.

ninavizz commented 3 years ago

Noting for when #5677 goes live... this should get resolved, too.