* Context - How has this issue affected you? What are you trying to accomplish? Providing context helps us come up with a solution that is most useful in the real world.
We are using The Whonix-devel Archives as much as possible if we communicate with e-mail based issue trackers such as Debian BTS, contact other e-mail lists or individuals. It’s a useful public archive of communications. Where could we add the link to our archive The Whonix-devel Archives in our wiki?
I made a few changes to the page. This might be a good alternative to a new page? I think it separates/defines the Qubes onionizing from the Non-Qubes onionizing sections. Please let me know if its likeable or not.
Now, if the long term goal is to separate projects as much as possible (Qubes from Non-Qubes) I can go ahead and move each to its own page. One again, please let me know.
Getting really good! Made some minor edits such as a consistent introduction text which could use critical review.
Take note that while Whonix ™ maintains both v2 and v3 onion addresses, it is strongly encouraged to prefer v3 .onion connections which provide additional improvements and security benefits over the v2 legacy system. [2]
Do we need this in introduction? Perhaps move to the Whonix repository template?
Since it is now split in a more user friendly way: i.e. split by the user able to choose its platform rather than package repository… For consistency… What do you think about to abolish the standalone, merge (duplicate) please Onionize Tor Project Updates into the both Whonix sections above? Or just briefly mention it and then have the onionized section at Installing Newer Tor Versions instead?
Other corner cases: What about Debian users who are using Whonix Packages for Debian Hosts and Whonix Host Enhancements or other custom repositories? Suggested solution: a section below introduction or better(?) a template for each platform (since specific Debian based vs Fedora based [dom0]) which: teaches the user and advises to manually review all repository configuration files?
It looks really good now. I like how Fedora stands out from the rest of the Qubes templates.
This part is what my eyes focus on:
Note: Updating Fedora templates exclusively over Onion Services is not possible.
Good idea (whonix repo template)
I like this idea (merge). That way there are two sections i.e. Qubes and Non-Qubes.
Each platform (Fedora, Debian ) can have an template instructing users to inspect/review repository config file. And what to look for when doing so. I think that would be a good idea.
I’m up to the task
Edit: Someone took care of the nits for me. I suspect torjunkie
Made a few changes to onionizing repositories. Merging the Onionizing Tor project updates didn’t work out. It just didn’t look right regardless of how it was formatted. I’m going to move to Installing Newer Tor Versions (tomorrow). Also working on the templates for inspecting the repository files. We currently have instructions to “test” repositories after onionizing, but beginners likely don’t know what that means.