> 'awokd' via qubes-users:
>>> Based on the settings I chose, should I have expected the
>>> qubes-dom0-update commands to leverage a Tor connection?
>>> Does it seem
>>> likely that they did in this case?
>> No; agree it doesn't sound like it. Did you "sudo qubesctl state.sls
>> qvm.updates-via-whonix" as part of upgrading the Whonix templates? Seems
>> like it should have been unnecessary, though.
> The only CLI tool I used was qubes-dom0-update, once for each template.
>>> In future, what steps can I take to
>>> verify that performing similar updates will use Tor?
>> Check Qubes Global Settings to make sure Dom0's UpdateVM is set to
>> sys-whonix. Also, double-check /etc/qubes-rpc/policy/qubes.UpdatesProxy
>> and make sure the first line says "$type:TemplateVM $default
> I'll check this and post back.
You were right, these were incorrectly set. I had to manually change
the Dom0 UpdateVM to Sys-Whonix, and uncomment the $type:TemplateVM
$default allow,target=sys-whonix line. I'll be performing a fresh
install of Qubes R4.0.1 on a friend's device with the same settings, if
this happens with hers too I'll report a bug.
I followed the Onionizing Repos guide, commented out the metalinks and
uncommented the onion lines. On first test (sudo qubes-dom0-update) I
got a 404 error:
> HTTP Error 404 - Not Found
> "Error: Cannot retrieve repository metadata for (repomd.xml) for repository: qubes-dom0-current"
The following text was in white instead of red, so it's possible the
other repos were successfully updated, but I'm not sure.
> Qubes OS Repository for Dom0 12 MB/s | 26kB 00:00
That was the end of the text echoed to the Console. Has that particular
file been moved and the yum.repos.d/qubes-dom0.repo file not been updated?