Please post here if there should be review #2. @torjunkie
Example of first time Linux in a VM user woes.
“Whonix is asking for host login” → https://www.reddit.com/r/Whonix/comments/b6qvjr/changing_password_in_whonix/
(An issue of not providing a unified experience.)
Trying to update @0brand’s e-mail address. Moderator status will be temporarily revoked (duration less than 1 hour most likely). Similarly the account will be deactivated for a very short period.
1 Like
As per:
User account @0brand deactivated, e-mail updated as per @0brand’s request, activation e-mail sent, (mod restored). After link the activation link, the account will be re-activated.
1 Like
On second thought this would be a better idea. If someone were to look at (https://github.com/orgs/Whonix/people) they might think Whonix is a single person project i.e. mostly Patrick’s commits in recent times. Even if looking at the Whonix Team page it would be difficult for other people (orgs) to tell from a glance:
a) who contributes. AND
b) what they contribute to the Whonix project.
This way it would be a simple matter to provide a link to the Official Online Profiles page. It could save time down the road if someone requests this information.
I’ll be creating my profile when I get the chance. 
1 Like
@Patrick Sure Whonix users don’t need to follow this, but people who want it on their hosts for more security and wider application will. Can you please revert?
1 Like
Are there reasons for not changing whonix clearnet instructions to also be over Tor?
tor+http
and also would need apt-transport-tor
https://www.whonix.org/wiki/Template:Whonix-APT-Repository-Add
The page is primarily read by Whonix users. These following that instructions would be confusing. So we can mention Debian users there but it needs to be done in a way that doesn’t lead Whonix users to applying https://www.whonix.org/wiki/Whonix_Packages_for_Debian_Host.
- Onions unreliability. No longer using onions by default in Whonix.
- More complex instructions for setting up the repository. Maybe not a good reason?
- How much is it worth connecting to Whonix repositories over onions when all other of users repositories are probably still using plain http? Maybe not a good reason?
Onions could be mentioned but I was wondering if that is not what the user is looking for in that moment, thus bouncing.
No problem - instructions are very nice and pretty clear (interested users can read the footnotes as you say for details).
Please give the wiki account Buffy power to edit templates and create new pages and I’ll do the rest. (will also fix up that Onion Gaming shit, which is annoying on that Onion Services page etc etc.)
BTW there are some protected templated pages which IMO shouldn’t be protected e.g. stylometry, that malware & trojans page etc. Generalist text that is only mentioned in one page should allow general user edits so they can be improved over time by the user base. Templates used in a 1,000 places - not so much.
I’ve added waterhole attack text to the firmware page → but I need to shift it to the “Malware and Trojans” page (since not specific to firmware where the pending edits are sitting). But waiting on template editing powers for that.
Thanks - will fix all that.
2 Likes
Great! 
Done.
Sure. Please update.
I meant changing the instructions for whonix clearnet repo to have its traffic routed thru Tor by adding tor+http://deb.whonix.org…
1 Like
Reasons for not using tor+http://deb.whonix.org on Whonix Packages for Debian Hosts and Whonix Host Enhancements :
- More complex instructions for Debian users for adding the Whonix repository. I.e. they need to install apt-transport-tor and also keep in mind Hide Tor use from the Internet Service Provider too? Maybe not a good reason?
- How much is it worth connecting to Whonix repositories over Tor when all other of users repositories are probably still using plain http over clearnet? Maybe not a good reason?
tor+http://deb.whonix.org could be mentioned but I was wondering if that is not what the user is looking for in that moment, thus bouncing.
The fact that safer defaults are not widely used is not a good argument IMO. It protects against version leak and user targetting also from additional attention that user John Doe knows about Whonix and is a user.
1 Like
Edit: I just went ahead and changed it. It seems like one small extra step for more privacy and should’t really interfere with anything.
1 Like
Guilt by Association
@HulaHoop i am not sure i am following what you are saying. this is to be added in what machine?
1 Like
These are for people adding Whonix repos on their hosts only.
1 Like
Whonix Documentation looking better and better!
Does Whonix Documentation still contain contents from Tails - Documentation? If not, we could get rid of {{License_Amnesia|{{FULLPAGENAME}}}}. Other ways to get out of it:
- Fair use.
- Common phrases. (First Steps with XXX or XXX First Steps are most likely not copyrightable.)
- I guess not too much rewording would be required to get rid of any residual contents by Tails.
Full Disk Encryption and Encrypted Images - Whonix has been split as discussed a while ago into:
- Full Disk Encryption (FDE) - practical, advisable
- Encrypted VM Images - asked sometimes, thoroughly thought through, theoretical
1 Like
If we want to declutter the main Documentation page further, what would work nicely would be shifting everything currently with “Advanced:…” to a sub-page.
When you look at most of those sections, they are either advanced or (more often IMO) just obscure activities e.g. nested virtualization, building from source, unsupported virtualizers and other random things. Probably 1/100 users do most of that, so I agree what one of the commentators on that page, it should be simplified.
So if we have an /wiki/Advanced/Documentation page I think all the following stuff should go there:
- Advanced: Esoteric Issues
- Advanced: File Transfers and SSH / SSHFS
- Advanced: Miscellaneous
- Advanced: Platform Support
- Advanced: Tor
- Advanced: Whonix-specific
(And we can also lose the ‘Advanced’ part in each title. If any stuff in those sections is either a) not advanced, or b) common, then simply link to it in the main ToC page instead. Definite rationalization required, otherwise the ToC looks overwhelming).
Appendix should probably stay on the main Documentation page as is.
Would be much cleaner, and less intimidating for ‘normal’ users i.e. 98% of people.
1 Like