All operating system update stuff fixed (very messy), plus millions of lines of spacing fixes etc.
(We really should have a separate Qubes update template of its own & not “borrow” the non-Qubes-Whonix one, but anyway)
1. DispVM half page half done (we need to watch the {{whonix-ws}} and {{whonix-gw}} code isn’t broken on multiple pages - I already discovered it in AppArmor section and DispVMs, so no doubt it is elsewhere.
2. Template: {{Tor_Browser_Remove_Proxy_Settings}} causes massive whitespace because of the last footnote in it for some reason.
I am not sure if we compress to much information into one sentence that
could lead to ever fewer users understanding this. While the sentence
may be technically concise, correct, it may still be less understood
than with more redundancy?
Made some changes:
new Debian release: “may”, “depending on deprecation notice” (in theory,
if I can’t make it work on the new release of Debian for some reason or
can’t switch myself for some reason then actually until that time
oldstable has to be used.)
new Whonix release: “will” (because then it’s clear that there is a new
Whonix release that is functional)
sub headline Debian Hosts, sub sub headline “New Whonix, Debian, Qubes
or Qubes-Whonix Release”, here I actually made a mistake. Debian hosts
have nothing to do with Qubes or Qubes-Whonix. Rewritten.
4. On this page below, you have: {{Template:Qubes}}, but nothing seems to appear? Delete or fix to get rid of whitespace etc?
Yes, legacy. Delete please.
Where do we report it? I’d like this fixed before they disappear for good (if possible).
That is the issue. Users can’t use both Qubes onion repos and Debian onions. If repos configured like that I’m not sure if any Qubes-Debian packages would be pulled from the http// URI instead of Debian onions? Likely if onions where down.
If repos configured like that I’m not sure if any Qubes-Debian packages would be pulled from the http// URI instead of Debian onions? Likely if onions where down.
I may be misunderstanding something but any onion should be possible to combine with any other onion. When using onions exclusively and Debian onion is offline then one would miss out on Debian package upgrades for sure.
It is unnecessary to apply these updates in standard Non-Qubes-Whonix and Qubes-Whonix guest VMs, as they do not have the ability to alter the microcode. However, processor microcode updates should always be applied on the host operating system (for processors by Intel or AMD) [3] and baremetal configurations like Physical Isolation. [4]
Everyone happy with the micro-edits?
Pretty well ready to smash email section down of the ToC now. And there is stuff that really needs work in those sections, to put it mildly.
It is unnecessary to apply these updates in standard Non-Qubes-Whonix and Qubes-Whonix guest VMs, as they do not have the ability to alter the microcode. However, processor microcode updates should always be applied on the host operating system (for processors by Intel or AMD) [3] and baremetal configurations like Physical Isolation. [4]
__NOTITLE__ should be transformed into a wiki template {{notitle}}. (https://www.whonix.org/wiki/Template:notitle) (If someone gets to it before me.) Mass replace doens’t work.
Empty template (just nothing but a page instead of non-exiting page) for now. Later I’ll add the wiki markup there for HideTitle as soon as I can make that work.
That protocol-leak-protection page has some good info. @Patrick
I think it should be tidied up, all the long code stuff etc split off into a separate page, and then put somewhere with pride on the main page. Right now it is in a dusty back room & probably not getting many eyeballs.
I’ve been using DisplayTitle to fix a ton of pages. Looks good.
Converting the HTTPS-Everywhere user rules sqlite3 binary file to plain text file for editing, then back to a binary file looked promising in the beginning but turned out to be a dead end. If anyone would like a go at it or could give some advice. The issue is in the last step. Somehow the file is changed when converting from plaintext file back to a sqlite3 binary file
1. Install sqlite
sudo apt-get install sqlite3
2. Dump the https-everywhere rules data base to a plain text file.
For most pages {{Footer}} sorts out licensing perfectly.
{{License_Amnesia {{FULLPAGENAME}}}} is only required for a few pages imported from Tails a few years ago. Only pages that already have that which then get moved elsewhere may require it.
Pages that have it such as /Documentation also contains something like:
<!--
The Whonix Documentation wiki page is forked from the Tails Documentation page, from this exact source <http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc.mdwn;hb=920ef988d1e8ed552f4e97d1423e0038e1bfbbf4>.
-->
Since years passed since then the link broke. Keep it anyhow as is. Not worth the effort. Copyright is being complied with. Still has enough information if someone wanted to dig. No one interested in this.
If we move content from such a page elsewhere we’d hack to check how the Tails page looked back then or looks now to see if we have to re-add that notice.
While we are at it… Does bitmessage belong to Email Overview? I mean shout it be on the Email Overview page? It’s not listed on Whonix Documentation which might make it hard to find. I am writing might since I don’t really know how someone who’s interested in Whonix and bitmessage would search and then find or fail to find.
More generally asking… Would you think the wiki gets more usable by moving more things into dedicated wiki pages?
Like on the Instant Messenger Chat page. HexChat has its own page while Gajim and others do not.
Noted - footer is enough.
I’m pressed for time atm so I’ll re-edit a little later on.