Qubes DispVM technical discussion

Patrick · June 14, 2018, 6:56am

In short: in Qubes-Whonix 14 after upgrades new AppVMs and DispVMs are created with a copy of the latest version of Tor Browser after tb-updater in whonix-ws TemplateVM was upgraded.

⚓ T726 if tb-updater storage path for Qubes R4 DispVMs is resolved in Qubes-Whonix 14 after upgrades
Tor Browser Essentials
Tor Browser Advanced Topics

tb-updater and /usr/bin/torbrowser will refuse to start in Qubes DVM Template. (Advanced users could overwrite the function easily using a config snippet but I doubt there is a use case.)

Patrick · June 15, 2018, 12:57am

Yay!

Qubes/Disposables: Difference between revisions - Whonix

Patrick · August 3, 2018, 10:05am

github.com/QubesOS/qubes-issues

document DVM Template / DisposableVM - Inheritance and Persistence

opened 10:04AM - 03 Aug 18 UTC

closed 08:28AM - 16 Aug 18 UTC

adrelanos

C: doc T: task

What does a DVM Template inherit upon creation? I guess `/etc/skel` to `/home`? … Which mount points do persist in a DVM Template after shutdown? I guess `/rw` and bind-dirs? Does a DisposableVM really only inherit `/home` or all of `/rw` (including `/home`, `/usr/local`, `/rw/config`)? I guess it inherits all of `/rw`? What about bind-dirs in DVM Template? What about bind-dirs in DisposableVM? I guess those won't make things persistent either way? ---- * https://www.qubes-os.org/doc/templates/#important-notes-r40 * https://www.whonix.org/wiki/Template:Qubes_persistence

Patrick · August 24, 2018, 4:30pm

Patrick · August 24, 2018, 4:32pm

Major update of documentation for DispVMs for Qubes R4 with Qubes-Whonix 14.

Has still quite some TODOs. Help welcome.

Bold changes. Lots of purges. If anything got missing in action it can be recovered from Outdated, Deprecated, Archived Whonix ™ Documentation. or from wiki history.

Patrick · September 10, 2018, 8:48am

github.com/QubesOS/qubes-issues

some DVM Templates should be non-networked by default for better security?

opened 08:48AM - 10 Sep 18 UTC

closed 04:45PM - 10 Sep 18 UTC

adrelanos

R: duplicate

Should some DVM Templates should be non-networked by default? Perhaps default… DVM Templates should be non-networked by default? Reasoning: similar reasoning like for making TemplateVMs non-networked by default. A compromised DVM Template would be inherited by all DispVMs based on that DVM Template. Would it therefore make sense to treat a DVM Template more like a TemplateVM?