Long Wiki Edit Thread

Yeah. Need to simplify that. Users struggle with things which are totally obvious for us.

At least 3 or 4 users did not manage to use Whonix because Whonix asks for “host login”. Users probably mean this screen.

First mistake perhaps, they downloaded Whonix CLI rather than Whonix XFCE?

Whonix for Windows, macOS, Linux inside VirtualBox and Whonix for Windows, macOS, Linux inside VirtualBox look quite alike. Links from all over the internet and people discussing various things might have users end up one the wrong page. So added a warning to the Whonix CLI page.

People then give the actual host (as in outside of the VM) login which obviously won’t work. Too bad.

agetty asks for “host” login since hostname was set to “host” for better anonymity.

If we could use hostname “Whonix-VM” that would be better for usability but worse for anonymity (then it would ask for “Whonix-VM login”).

We could improve the messages above.

But I haven’t found a way yet to make agetty ask for something other than “$hostname login”.

The next thing users will stumble on and give up is the absence of asterisk stars * as users type their password.

Qubes onions are back, please check Onionizing Repositories.

Since you agree then I’ll shift all those “Advanced” bits and pieces to an “Advanced Documentation” page. Stop me now if you don’t want that…

Looks good. I see adw made some edits too - thanks adw :slight_smile:

Agree that simple Qs in forums like this indicate documentation needs to fill that gap - backing up what people were saying about quick start guides etc. ‘Normal’ users have very simple expectations in the main.

1 Like

Could you split Multiple Qubes-Whonix TemplateVMs from https://www.whonix.org/wiki/Multiple_Whonix_Gateways_and_TemplateVMs to its own page too please? (Also a workstation template can be cloned.)

The reason I didn’t do that originally was because of the small size of the text/content attached to Multiple Whonix-Gateways i.e. would have been a tiny page? You still want to do that?

1 Like

I guess we have to in this case? Multiple-Whonix-Workstation’s didn’t fit multiple Whonix-Gateway’s or TemplateVMs. So if we split it, we should split for good for consistency.

Perhaps it fits best into /Qubes/ somewhere?

in this wiki:

i have delete video & audio editing tools because they were KDE based. anyone has better alternatives? (better to be DE free dependencies or Xfce based)

1 Like

For pre-installation it’s nice if we can reasonably stick with XFCE only (reasons of disk space and maybe some other reasons). However, generally it’s not a problem if users mix packages of GTK, QT, LXDE, Gnome, Mate, KDE and whatever. If some user wants for example kwave, there is no reason to discourage that. So if there are no replacements for those, we can just keep the kde ones there. Or should the kde ones (just speaking theoretical) be better than anything else, another reason to leave them there.

any reason not to config the cli version to autologin “user” on boot?

Yes. I was considering it. When there is autologin it would also apply to:

  • physical isolation (autologin there would be surely criticized as security issue)
  • Non-Qubes-Whonix XFCE version: autologin for desktop is obvious and can be disabled but tty1 autologin would be a bad surprise to those who disable autologin for the desktop.
  • Is it worth it? Are those who get confused by host login the same users who accidentally downloaded the CLI rather than XFCE version and those users would be stranded after autologin anyhow?

Not easy to enable autologin for some versions only. Might require a new package which gets installed on CLI only.

Soon I will include Zulucrypt a LUKS container utility similar to Veracrypt but with the good ol’ dmcrypt on Linux.

What is a good place to document it?

1 Like

Note: that will be Non-Qubes-Whonix only.

All fixed and split.

Please delete the old page → http://www.whonix.org/wiki/Multiple_Whonix_Gateways_and_TemplateVMs

All fixed.

2 Likes

Done.

1 Like

Thanks

2 Likes

Thanks to you. You are the one doing the work :slight_smile:

1 Like

Should https://www.whonix.org/wiki/Template:Known_bugs be refreshed to remove all the bugs that have been fixed/worked around?

1 Like

HulaHoop via Whonix Forum:

Should https://www.whonix.org/wiki/Template:Known_bugs be refreshed to remove all the bugs that have been fixed/worked around?

Sure.

Note: Whonix 14 only bugs can be marked as such (helpful for later
removal) but only removed once Whonix 14 is released for all platforms.

On that Testers ([[Test]]) page, the empty < pre> fields are annoying visually.

If the steps can’t be done with CLI, just better to bullet point those ones.

If there is any left that can be done with CLI, I’m sure you have the magic skills to do it :slight_smile:

1 Like