i was hacked? what to do?
This is something that happens from time to time. The good news is, this doesn’t look like you’ve been hacked. Quite often this is something that resolves itself in time.
Taken from wiki Security_Guide
It could be a temporary Tor exit relay or server failure that should resolve itself. Check if the network connection is functional by changing the Tor circuit and trying again. Running whonixcheck might also help to diagnose the problem.
Have you successfully updated your R4.0 Whonix templates prior to this?
Did you change any network settings recently?
thanks for the help! now a new problem. can not update fedora 26
Since this issue in not Whonix specific you can use the Qubes mailing list to ask for help with updating Qubes (Fedora) templates.
If you do ask for help on the Qubes mailing list it may be helpful to:
- translate the text in the Fedora terminal to english
- mention if this is a new problem ( have you successfully updated this template previously?)
- if you changed any network settings
Also, if you are updating over Tor? You may want to wait a while and try again.
Modify /etc/yum.repos.d/qubes-r4.repo to use https instead of http.
thanks for the tips! the problem decided. There is one more problem. on the picture, the arrow shows that it requires an update. how to update it? as well as the rest template or was peculiar?
This following wiki page was written for Qubes 3.2 .
If you are using Qubes 4.0, you can disregard setting a NetVM for your template VMs. (Github Qubes issue 1854)
There is also an issue with
qubes-manager showing the pending updates available icon (green arrow) when no updates are available. If you have already updated Whonix templates, its most likely due to this bug.
I do not understand how to update the tor browser in whonix-vm-dvm?
Updating Tor Browser should be fairly simple
Edited as per Patrick’s followup post
dom0, run Tor Browser in
2. In the upper left hand corner of Tor Browser, right-click the green onion. 3. Right-click on Check for Tor Browser updates 4. When updates are complete, restart Tor Browser when prompted 5. In
qvm-run whonix-vm-dvm konsole
whonix-vm-dvmkonsole, update Tor Browser
Don’t start Tor Browser in TemplateVM. This is at least what we write here:
Open to reconsider.
This is not yet well thought through / let alone documented. TODO: development
Thank you very much, you helped me. I corrected everything!
Eventually, the (Anondist) Tor Browser package will be updated within the
template with regular updates, right?
I update Fedor 26 and that’s what’s on the screen, what does it mean? all OK?
Otherwise, this is up to Qubes support as per:
1st and 3rd pics are not unusual. You often see similar output with Qubes package updates.
2nd pic is a known issue that is fixed in Whonix 14. See:
It is not fatal to anonymity. If you run:
systemctl status systemd-timesyncd.service
You will see the process is dead ->
user@host:~$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: inactive (dead)
PS Jessie is EOL as of 17 June, so I guess we don’t have long to wait for Whonix 14 ->
Your earlier pics re: Fedora 26 updates and checksums not matching is also not uncommon. As to why - I’m guessing it relates to issues Qubes have had recently re: changing Fedora repos to https, or possibly network attackers at large screwing with downloads over Tor (although I don’t see how it can succeed as an attack vector, if
gpgcheck=1 is applied, which it is by default).
Please use the search function of the forums or search engines to search for error messages. Very likely you’re not the only one affected and very likely has been discuses beforehand. Like in this case. Example search term:
unexpected result by timedatectl
Summary: harmless and fixed in Whonix 14