I do this, but I use a squid proxy setup from rustybird to cache updates.
Starting up and shutting down VMs still takes the same amount of time though.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
(By "local install" I mean per-user install)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on
My (perhaps naive) approach is to just use flatpak local install in the
AppVM. I don't have to mess with bind-dirs. I have a couple different
AppVMs where I have such proprietary software away from anything I want to
keep safe/private. I'm curious why people are talking about reinstalling on
On 9/3/20 12:44 AM, 'Ryan Tate' via qubes-users wrote:
I've started making special templateVMs where I install less trusted
software, typically closed source binaries or code distributed directly
from a vendor.
I am curious if others do this and if people think it adds much security
wise.
On 9/2/20 11:39 PM, airelemental via qubes-users wrote:
I just don't like the idea of putting untrusted code in a templateVM used by
sensitive VMs.
Me neither! But I avoid multiplying templates by installing apps directly into
appvms.
This minimizes the number of templates I have to keep
> I just don't like the idea of putting untrusted code in a templateVM used by
> sensitive VMs.
>
Me neither! But I avoid multiplying templates by installing apps directly into
appvms.
This minimizes the number of templates I have to keep up-to-date.
> fedora-32-zoom (the proprietary
I've started making special templateVMs where I install less
trusted software, typically closed source binaries or code
distributed directly from a vendor.
I am curious if others do this and if people think it adds much
security wise.
For example, in addition to vanilla fedora-32, where I
