How can I prevent qubes that connect to clearnet from downloading repositories?

Hello
I read the information on the website

I have doubts about the content of preventing qubes connecting to clearnet from downloading repository metadata.

Nowadays, things have changed a bit in Qubes and I don’t know what to do to avoid downloading repository metadata through qubes that connect to the clearnet network.

When you enter:
Qube Manager->System->Global Config-> Updates->Check for qube updates

I have the following things:
Selected Check for and notify me about dom0 updates

Here I have a message:
The setting below will be applied only to existing qubes. New qubes have checking for updates enabled by default.

Selected Enable checking for updates for all existing qubes

Not selected Disable checking for updates for all existing qubes

Not selected Except the following qubes, for which checking for updates will be disabled

What should I tick?
What’s next in the case of creating new qubes?

As for the second part of the instructions on the kicksecure website, after entering:
Qubes Manager->Right-click Template->Qubes settings->Services

I don’t have qubes-update-check checked so I don’t have anything to uncheck. In fact, I don’t have anything marked on the list of services. I checked in the template debian 12 (it’s my default template).

What should I do in this situation?

I’m asking a question on the Whonix forum because I found these instructions here(as shown by the Re: [qubes-users] Update checking over clearnet instead of Tor? member of the Qubes core team Marek Marczykowski-Górecki sees no problem in downloading repository metadata by quby connected to clearnet). I will add that I do not use kicksecure but whonix in the Qubes system. My update proxy is sys-whonix.

Please help

1 Like

Duplicate of Update (TemplateVM, dom0) over Tor / torify all of Qubes traffic?

1 Like