Long Wiki Edits Thread

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 :wink:

Edit: Someone took care of the nits for me. I suspect torjunkie :slight_smile:

1 Like

Looks much better. Agree with you that merging might be better.

Re: GSOD - well done guys and gals on acceptance and interest already in forums from computer science students etc. +1 :slight_smile:


https://www.whonix.org/w/index.php?title=Tor_Browser&type=revision&diff=47025&oldid=47024 awesome, thanks for the notice! Yes, if we can, keeping users up to date on current events provides immense value. Turned this into a news too.

A post was merged into an existing topic: TODO research and document - How to use Tor Browser for security not anonymity? How to use TBB using clearnet?

It would be a big help If we could rebrand/rename the browser. It really is a

  • Hardened browser
  • Security hardened browser
  • Advanced security browser
  • Security focused browser (don’t like this one)

How about adding this to qubes documentation? Maybe just to the Whonix section at first?

Not right now, sometime in the future I could.


0brand via Whonix Forum:

How about adding this to qubes documentation?

Great idea!

That would give it more exposure.

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 https://www.whonix.org/wiki/Tor_Versioning (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.


1 Like

Does https://www.whonix.org/wiki/Install_Software#GUI_Applications_with_Root_Rights belong to that page?

Migrated Tor Project Updates to Tor Versioning.



1 Like

Could you add content to https://www.whonix.org/wiki/Hardware_Threat_Minimization#Speaker please? @HulaHoop

1 Like

@HulaHoop i cant install or do any step with your installation instructions. Please whenever you are free update your instructions to be fitting with Debian Buster as a host.

1 Like

To make sure users are clear it’s non-Tor, I’d add “clearnet” somewhere (or perhaps another “non-Tor” synonym if there is any).

  • Hardened Clearnet Browser
  • Secure Clearnet Browser

These links added in https://www.whonix.org/w/index.php?title=Tor_Browser&oldid=47110&diff=cur conflicts with the Whonix way of getting new versions (Tor Browser Updater by Whonix developer).

What step exactly? I always update the guide to follow what Debian version is stable at the moment.

1 Like

The leaks mentioned in https://www.whonix.org/wiki/File_Sharing#The_Tor_Project only apply when used outside of Whonix. At the moment it sounds like Whonix users would be affected too. Can we point that out without making it an invitation?

Found the perfect spot for Tor Browser without Tor. I’ll rename this page Security / privacy enhanced browsers.

I’ll have to modify the the content for Qubes but most of the page can be copied as is (with attribution).

1 Like

--baseuri is unfortunately not implemented. I didn’t have ideas how to do it back then. Perhaps standardize instructions and have user do it manually similar to all other instructions?

That would be easier for users unfamiliar with Whonix apt repo.

1 Like

The issue of burdensome and repetitive instructions on a single page regarding the different ways to edit a text file was discussed before. I was recently surprised to find this taking place even on the KVM installation instructions page.

I would like to suggest the following be added to the top of every guide-style page that requires editing text files:

Editing text files
In this guide [/page] we use nano [optional: link to a very quick guide, added below] as a text editor. If you prefer a graphical editor use mousepad (on XFCE) or kwrite (on KDE).
For example, instead of:

nano filename [or always sudo nano?]


kdesudo mousepad filename

Then, all the instructions throughout the page will only use nano instead of the repeated clause "if you are using… then… ".

To make things more friendly I wrote the following “very quick guide” mentioned above (should appear on a dedicated page, containing only that):

Nano is a popular and simple text editor in Linux. Basic usage:

  • Open the file for editing by typing in terminal:

nano filename

  • If the file was created by root, we need to use sudo to get proper privileges:

sudo nano filename

  • If you try to edit a file that does not exist, nano will create the file.

Essential keyboard shortcuts:

  • To save: CTRL-O
  • To Exit: CTRL-X
  • Moving the cursor is done using the arrow keys or Page Up and Page Down. Mouse click does not move the cursor.

More keyboard shortcuts:

  • To delete a full line: move to that line, then press CTRL-K
  • To search: press CTRL-W, then type the text you wish to find, then ENTER.

Formatting can be improved of course.
More can be added, but I think it’s unnecessary. Better keep it short. Even the search function is probably not required for the tasks users are expected to follow throughout the guides. We may add:

For the complete features, type

man nano

1 Like
[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Contributors] [Investors] [Priority Support] [Professional Support]