Update Qubes-Whonix ™
From Whonix
< Qubes
Contents
End-of-life Software[edit]
Users should not run software that has reached end-of-life status, because developers will not fix existing defects, bugs or vulnerabilities, posing serious security risks.
A recent example was VLC in Debian jessie [archive], which reached end-of-life status in May, 2018. In that case, Whonix 13 users who did not utilize a different media player were at risk, because VLC in jessie has unpatched security vulnerabilities. This VLC vulnerability does not apply to the current stable Whonix 15 release.
Installing Additional Software[edit]
See Install Software.
Updates[edit]
Standard Upgrade vs Release Upgrade[edit]
This procedure is for every day upgrading of Qubes-Whonix ™ and will not perform a Release Upgrade.
If a message like this appears.
WARNING: Whonix News Result:
✘ Outdated: Installed whonix-gateway-packages-dependencies 3.4.2-1 is outdated!
WARNING: Whonix News Result:
✘ Outdated: Installed whonix-workstation-packages-dependencies 3.4.2-1 is outdated!
Then most likely a Release Upgrade is necessary.
Before applying a release upgrade, it is useful to first complete a standard upgrade in both the whonix-gw-15 and whonix-ws-15 TemplateVMs, via Konsole:
Qubes App Menu(blue/grey "Q")→Template: whonix-gw-15→KonsoleQubes App Menu(blue/grey "Q")→Template: whonix-ws-15→Konsole
Then perform the Standard Upgrade Steps below in both terminals.
Standard Upgrade Steps[edit]
Note: Updating Tor Browser is a separate issue; see Update Tor Browser.
1. Update the Package Lists
At least once a day, Qubes users should update the system package lists in all TemplateVMs, Standalone VMs and dom0 with the latest version information on new and updated packages that are available for download. [1]
To update the whonix-gw-15 and whonix-ws-15 TemplateVM packages lists, simplest is using Qube Manager:
Qube Manager → left-click whonix-gw-15 or whonix-ws-15 → Update qube system (blue arrow)
Alternatively, open a terminal in the TemplateVM and run.
sudo apt-get update
The output should look similar to this.
sudo apt-get update Hit:1 tor+https://cdn-aws.deb.debian.org/debian-security buster/updates InRelease Hit:2 tor+https://deb.whonix.org buster InRelease Hit:3 https://deb.qubes-os.org/r4.0/vm buster InRelease Hit:4 tor+https://cdn-aws.deb.debian.org/debian buster InRelease Reading package lists... Done
If an error message like this appears. [2]
Ign:1 http://ftp.us.debian.org/debian stretch InRelease Hit:2 http://deb.qubes-os.org/r4.0/vm stretch InRelease ... Err:12 tor+http://sgvtcaew4bxjd7ln.onion stretch/updates Release Connection failed Reading package lists... Done E: The repository 'tor+http://sgvtcaew4bxjd7ln.onion stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Done.
Or this.
500 Unable to connect
Then something went wrong. It could be:
- A temporary Tor exit relay or server failure that should resolve itself; or
- One or more Onion Services might be non-functional.
In the first case, check if the network connection is functional by changing the Tor circuit and/or run whonixcheck to try and diagnose the problem. In the second case, try setting clearnet repository links before attempting to update again.
Sometimes a message like this will appear.
Could not resolve 'security.debian.org'
It that case, it helps to run.
nslookup security.debian.org
And then try again.
2. Upgrade
If using a terminal, run the following command to install the latest system package versions. [3]
sudo apt-get dist-upgrade
Please note that if the Whonix APT Repository was disabled (see Disable Whonix APT Repository), then manual checks are required for new Whonix releases along with manual installation from source code.
3. Never Install Unsigned Packages!
If a message like this appears.
WARNING: The following packages cannot be authenticated! thunderbird Install these packages without verification [y/N]?
Then do not proceed! Press N and <enter>. Running apt-get update again should fix the problem. If not, something is broken or it is a Man-in-the-Middle Attack, which is not that unlikely since updates are retrieved over Tor exit relays and some of them are malicious. Changing the Tor circuit is recommended if this message appears.
4. Signature Verification Warnings
There should be no signature verification warnings at present; if it occurs, it will look similar to this.
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.torproject.org stable Release: The following signatures were invalid: KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681
Caution is required in this case, even though apt-get will automatically ignore repositories with expired keys or signatures, and no upgrades will be received from that repository. Unless the issue is already known or documented, it should be reported for further investigation.
There are two possible reasons why this could happen. Either there is an issue with the repository that the maintainers have yet to fix or the user is the victim of a Man-in-the-Middle Attack. [4] The latter is not a big issue, since no malicious packages are installed. Further, it may automatically resolve itself after a period of time when a different, non-malicious Tor exit relay is used, or following a manual change of the Tor circuit.
In the past, various apt repositories were signed with an expired key. To inspect how the documentation appeared at that point, please click on Expand on the right.
For instance, the Tor Project's apt repository key had expired [archive] and the following warning appeared.
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.torproject.org stable Release: The following signatures were invalid: KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 W: Failed to fetch http://deb.torproject.org/torproject.org/dists/stable/Release W: Some index files failed to download. They have been ignored, or old ones used instead.
This issue had already been reported [archive]. There was no immediate danger and it could have safely been ignored. Just make sure to never install unsigned packages as explained above.
For another example, see the more recent Whonix apt repository keyexpired error.
Although an unlikely outcome, please report any other signature verification errors if/when they appear.
5. Changed Configuration Files
If a message like this appears.
Setting up ifupdown ...
Configuration file `/etc/network/interfaces'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** interfaces (Y/I/N/O/D/Z) [default=N] ? N
Be careful. If the updated file is not coming from a Whonix ™-specific package (some are called whonix-...), then press n. Otherwise, Whonix settings affecting anonymity, privacy, and security might be lost. Advanced users who know better can of course manually check the differences and merge them.
To determine if the file is coming from a Whonix ™-specific package or not, follow this advice:
- Whonix ™-specific packages are sometimes called whonix-.... In the example above it states "Setting up ifupdown ...", so the file does not come from a Whonix ™-specific package. In this case it is recommended to press n as previously advised.
- If the package name includes whonix-..., it is a Whonix ™-specific package. In that case, it is safest to press y, but any customized settings will be lost (these can be re-added afterwards). Conflicts like these are relatively rare if Whonix's modular flexible .d style configuration folders are used.
6. Shutdown the TemplateVM
Shutdown the TemplateVM from Qube Manager: Qube Manager → right-click on TemplateVM → Shutdown VM or via the contextual menu.
7. Restart/Update Whonix VMs
If new updates were available and installed, it is necessary to either:
- Restart any running Whonix-Gateway ™ ProxyVMs (
sys-whonix) or Whonix-Workstation ™ AppVM instances (anon-whonix) so they are updated; or - Apply the same update process in any running VMs if an immediate restart is inconvenient.
Note: If any dom0 packages were upgraded during Qubes system updates, reboot the computer to profit from any security updates.
Non-functional Onion Services[edit]
Sometimes the Debian, Whonix or Qubes onion servers are non-functional, meaning updates cannot be completed automatically. In that case, an error message similar to the following will appear.
user@host:~$ sudo apt-get update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion buster InRelease Ign:3 http://ftp.us.debian.org/debian buster InRelease Hit:4 http://deb.whonix.org buster InRelease Hit:5 http://ftp.us.debian.org/debian buster Release Err:7 tor+http://sgvtcaew4bxjd7ln.onion buster/updates InRelease SOCKS proxy socks5h://localhost:9050 could not connect to sgvtcaew4bxjd7ln.onion (0.0.0.0:0) due to: Host unreachable (6) Err:8 tor+http://vwakviie2ienjx6t.onion/debian buster InRelease SOCKS proxy socks5h://localhost:9050 could not connect to vwakviie2ienjx6t.onion (0.0.0.0:0) due to: Host unreachable (6) Reading package lists… Done W: Failed to fetch tor+http://sgvtcaew4bxjd7ln.onion/dists/buster/updates/InRelease SOCKS proxy socks5h://localhost:9050 could not connect to sgvtcaew4bxjd7ln.onion (0.0.0.0:0) due to: Host unreachable (6) W: Failed to fetch tor+http://vwakviie2ienjx6t.onion/debian/dists/buster/InRelease SOCKS proxy socks5h://localhost:9050 could not connect to vwakviie2ienjx6t.onion (0.0.0.0:0) due to: Host unreachable (6) W: Some index files failed to download. They have been ignored, or old ones used instead.
To circumvent this issue until the onion service is re-established, complete the following steps in Whonix-Gateway ™ (whonix-gw-15) and Whonix-Workstation ™ (whonix-ws-15). [5] [6]
1. Open Debian sources.list in an editor.
Open file /etc/apt/sources.list.d/debian.list in an editor with root rights.
(Qubes-Whonix ™: In TemplateVM)
This box uses sudoedit for better security [archive]. This is an example and other tools could also achieve the same goal. If this example does not work for you or if you are not using Whonix, please refer to this link.
sudoedit /etc/apt/sources.list.d/debian.list
2. Comment (#) the lines with the .onion address and uncomment the lines with the clearnet address.
The first two code blocks should look like this. Note: only blocks shown need to be edited.
#deb tor+http://sgvtcaew4bxjd7ln.onion buster/updates main contrib non-free deb tor+https://deb.debian.org/debian-security/ buster/updates main contrib non-free #deb tor+http://vwakviie2ienjx6t.onion/debian buster main contrib non-free deb tor+https://deb.debian.org/debian buster main contrib non-free
Save and exit.
3. Confirm the clearnet repositories are functional.
sudo apt-get update
4. Revert and update the package lists.
It is recommended to revert these changes later on due to the security advantages of onion repositories. Afterwards, apply Updates to refresh the package lists.
Updating with Extra Care[edit]
See How-to: Install or Update with Utmost Caution.
Footnotes[edit]
- ↑ See: Installing and updating software in VMs [archive].
- ↑ https://forums.whonix.org/t/cant-update-any-whonixvm-in-qubes-4-0-or-whonixcheck/6023 [archive]
- ↑ Steps 1 and 2 can be combined with:
sudo apt-get-update-plus dist-upgrade - ↑ Rollback or indefinite freeze attacks as defined by The Update Framework (TUF) - Threat Model - Attacks and Weaknesses - https://github.com/theupdateframework/tuf/blob/develop/SECURITY.md [archive] - http://www.webcitation.org/6F7Io2ncN [archive].
- ↑ If similar problems are experienced with Whonix or Qubes onion services then the same procedure can be used to modify the
whonix.listandqubes-r4.listfiles, respectively. - ↑ http://forums.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/t/errors-updating-september-2018/6028 [archive]
Whonix ™ is Supported by Evolution Host DDoS Protected VPS. Stay private and get your VPS with Bitcoin or Monero.
There are five different options [archive] for subscribing to Whonix source code changes.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation.
Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee [archive] of the Open Invention Network [archive]. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)
Whonix ™ is a derivative of and not affiliated with Debian [archive]. Debian is a registered trademark [archive] owned by Software in the Public Interest, Inc [archive].
Whonix ™ is produced independently from the Tor® [archive] anonymity software and carries no guarantee from The Tor Project [archive] about quality, suitability or anything else.
By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent. Whonix ™ is provided by ENCRYPTED SUPPORT LP. See Imprint.