Process followed to the letter (assuming that I was actually supposed to update debian-11 via whonix ‘upgrade-nonroot’ method). (dom0 → Qubes VM Manager → right click ‘sys-whonix’ → Shutdown VM)" Shutdown and restart this TemplateBased ProxyVM. (dom0 → Qubes VM Manager → right click ‘whonix-gw-16’ → Shutdown VM) (dom0 → Start Menu → Template: whonix-gw-16 → Terminal) Please manually check inside your 'whonix-gw-16- TemplateVM WARNING: Debian Package Update Check Result: Could not check for someware updates! (apt-get-code: 100) If you want to change this, use:ĭom) → Start Menu → whonix-gw-16 → Whonix Repository Please read https:to understand the risk. When the Whonix team releases BULLSEYE updates, they will be AUTOMATICALLY installed (when you run apt-get-dist-upgrade) along with packages from the Debian team. " systemcheck | Whonix-Gateway | Whonix-gw-16 TemplateBased ProxyVM (Note: this is the header in black) I’ve seen it before on installs but previously have committed the cardinal sin of clicking to accept without first reading. Is it possible these two processes collided?ĭuring the update described above via GUI updater, a pop-up window appeared. Whilst going through update process: I also went about allowing tor set-up over standard channels (that is- no proxy or bridges). QUESTION: was that a mistake? Should I have waited on other processes to engage with the updater? I think maybe? See below. I selected box to update qubes without known updates and ticked all the boxes. My first move was to launch the qubes update tool via GUI. Install preferences irrelevant unless otherwise informed by those in the know. Not my first go with qubes, but testing re-install on other device to consolidate knowledge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |