Step 2.1:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-core-admin-addon-whonix
Complains that there is no match. Is this Qubes 4.0 only?
Step 2.1:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-core-admin-addon-whonix
Complains that there is no match. Is this Qubes 4.0 only?
I ignored the problem in Step 2.1 and went on:
Step 2.2
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-release
Says Skip one package
as it is already installed. However, there is no [qubes-templates-itl-testing]
section, and no /etc/yum.repos.d/qubes-templates.repo.rpmnew
.
Note: I was testing on Qubes 3.2
Fixed by running sudo qubes-dom0-update
Step 4:
sudo qubesctl state.sls qvm.anon-whonix
I executed it once without deleting the existing sys-whonix
, and the existing sys-whonix
remained unchanged. Then I deleted sys-whonix
and executed the command again. I got a brand new sys-whonix
.
Note: I need to manually configure the templates whonix-gw-14
and whonix-ws-14
to use sys-whonix
as NetVM. Since it’s been documented, Update Qubes-Whonix ™, I think it’s fair.
iry:
Step 2.1:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-core-admin-addon-whonix
Complains that there is no match. Is this Qubes 4.0 only?
Yes. Documentation updated.
I didn’t set sys-whonix
as my UpdateVM/ClockVM/netVM, however, sys-whonix
is auto-started at every boot of Qubes now.
Is this the expected default behavior? People argues that Issues · QubesOS/qubes-issues · GitHub
This can weaken the anonymity, if one connects automatically to different Networks with the same sys-whonix VM because of the same entry guards.
To disable the auto-start:
iry:
I ignored the problem in Step 2.1 and went on:
Step 2.2
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-release
Says
Skip one package
as it is already installed. However, there is no[qubes-templates-itl-testing]
section, and no/etc/yum.repos.d/qubes-templates.repo.rpmnew
.
Note: I was testing on Qubes 3.2
[quote=“iry, post:3, topic:5529”]
SaysSkip one package
as it is already installed. However, there is
no[qubes-templates-itl-testing]
section, and no
/etc/yum.repos.d/qubes-templates.repo.rpmnew
.
[/quote]Fixed by running
sudo qubes-dom0-update
Alright, can’t explain this but I added to the very top:
Update Qubes dom0.
sudo qubes-dom0-update
Can’t be wrong to update Qubes before anything else.
iry:
Note: I need to manually configure the templates
whonix-gw-14
andwhonix-ws-14
to usesys-whonix
as NetVM. Since it’s been documented, Update Qubes-Whonix, I think it’s fair.
Yes. Anyhow I guess it will generate a ton of confusion. Usability issue
on Qubes R3.2. The proper way to fix this would be the following but not
sure if realistic to happen:
iry:
I didn’t set
sys-whonix
as my UpdateVM/ClockVM/netVM, however,sys-whonix
is auto-started at every boot of Qubes now.Is this the expected default behavior?
Expected.
People argues that Cannot deactivate automatically start default netvm on boot. · Issue #3554 · QubesOS/qubes-issues · GitHub
This can weaken the anonymity, if one connects automatically to different Networks with the same sys-whonix VM because of the same entry guards.
Reference: Tor Documentation for Whonix Users
I tried to follow the steps at HowTo: Install the Testers-Only Version of Qubes-Whonix ™
However, in section ‘Qubes R4 Only’, this fails:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing mgmt-salt-dom0-virtual-machines
Error is:
No match for argument: mgmt-salt-dom0-virtual-machines
Error: Unable to find a match
The subsequent command sudo qubesctl top.enable qvm.whonix-testing pillar=true
also then fails with salt.exceptions.SaltRenderError: Could not find relpath for qvm.whonix-testing.top
It looks as though the package name is actually
qubes-mgmt-salt-dom0-virtual-machines
I also had to add --best --allowerasing
to force the upgrade to 4.0.0.13-1.fc25 from 40.0.11-1.fc25 due to apparent ‘conflicts’ (though it wasn’t clear what conflicts they were)
Section “Add Qubes’ Community Templates Testing Repository” :
Ensure the file contains
[qubes-templates-itl-testing]
minor note, this should be “Ensure the file contains [qubes-templates-community-testing]” because the text pasted beneath it is for templates-community-testing. (or, the text pasted beneath is incorrect, and should be that of qubes-templates-itl-testing. Whichever is true).
I have both qubes-templates-itl-testing and qubes-templates-community-testing in my qubes-templates.repo.
mig5:
Section “Add Qubes’ Community Templates Testing Repository” :
Ensure the file contains
[qubes-templates-itl-testing]
minor note, this should be “Ensure the file contains [qubes-templates-community-testing]” because the text pasted beneath it is for templates-community-testing. (or, the text pasted beneath is incorrect, and should be that of qubes-templates-itl-testing. Whichever is true).
I have both qubes-templates-itl-testing and qubes-templates-community-testing in my qubes-templates.repo.
Fixed.
mig5:
It looks as though the package name is actually
qubes-mgmt-salt-dom0-virtual-machines
Fixed.
iry:
Step 4:
sudo qubesctl state.sls qvm.anon-whonix
I executed it once without deleting the existing
sys-whonix
, and the existingsys-whonix
remained unchanged. Then I deletedsys-whonix
and executed the command again. I got a brand newsys-whonix
.
This is addressed for now through:
How-to: Install Qubes-Whonix
But I don’t like that solution. Could you report a bug to Qubes please?
Sure thing, done: