I used the normal command line terminal to update like apt update && apt upgrade for Debian, dnf update for Fedora and qubes-dom0-update for dom0. However, I found out about this command: sudo qubesctl --show-output --skip-dom0 --templates state.sls update.qubes-vm Basically what it does is upda…

I asked a similar question here: Improved support for interactive updates opened 04:14PM - 20 May 21 UTC (UTC) [DemiMarie] DemiMarie T: enhancement …

Thanks for your provided GitHub issue link. Personally, it would be enough for me if an error is displayed and nothing happens. Then I can go to TemplateVM and fix it myself. I want to have full control over my updates. As far as I know, this is not possible with non-interactive updates. [imag…

Thanks for your provided GitHub issue link. Personally, it would be enough for me if an error is displayed and nothing happens. Then I can go to TemplateVM and fix it myself. I want to have full control over my updates. As far as I know, this is not possible with non-interactive updates. [ima…

(made the title more specific about the issue discussed)

Thanks. My point about fingerprinting: if the repo server gets update hits in a certain pattern, that information can potentially be correlated with how many VMs a user has in use.

Anyone monitoring your internet activity would be able to get this information even if you use random sleeps between updates. The only way to avoid leaking that information would be to use a caching proxy and Tor.

What do you mean by a caching proxy? I am a big fan of Whonix. I do all my updates with Whonix (Tor).

A caching proxy is a proxy that stores the packages, so that other calls for the same package are serviced from the proxy instead of from the internet. tinyproxy, used by Qubes, does not cache. If you have many templates using the same repositories, (many cloned Debian templates, for example), …

Qubes OS Forum

Update via SaltStack: What Happens on Interactive Updates?

User Support

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled