In the wiki TOC the page is referred to as “Leak Protection” and I misunderstood what content belonged in there . I’m not able to find where I referred to it as fingerprinting but if I did I apologize. Regardless I wasn’t referring to the page by its actual name so thats why the confusion.
This was my fault, I need to work on communicating better. I know its important that you’re given the information you need to make informed decisions and you can’t do that if contributers/helpers aren’t providing you with it (or incorrect information). Sorry, my bad.
I’ll do a little fine tuning on the current (actual) page. Could you clarify what you mean by something going wrong outside of Whonix where Whonix is fine. I will add content on that.
I think for now in “Design” . A good page to reference when answering forum questions.
Taking the time simply to find a home may be a waste of resources vs. intent on writing something specifically for a wiki page. If a place for the content is eventually found, I will be more than happy to relocate it.
Also from now on I will post (detailed) what I am doing so no miscommunication.
Yes, fits nicely. Some of the content in new page will have to be taken out but most will fit into current “/Dev/Technical Introduction” sub headings IMO
We now have enough content for a shiny new documentation page. Do you think it would be good to move the content to the separate page? Printing and Scanning - Whonix
A minor comment on Software Recommendations
Why re-create that VM every time? If it gets infected by malware, it would probably get infected every time by the same malware?
if driver installation is the source: yes
if the printed file is the source: no
That chapter Software Recommendations is very good to have. Could you please copy it to make a generalized chapter “software installation TemplateBasedVM AppVM”. The idea is:
keep it mostly as is
have a custom script that that VM that does something like add repository, add signing key, apt-get update and apt-get install
do this every time that AppVM is started
Wastes some network traffic (but ok for many) but better than StandaloneVM. Combines TemplateBasedVMs’s advantages (little disk space and centralized updates) with “quasi full persistence”. For many applications such as signal or wire this works great. Their application data stays in the home folder and the application gets easily installed by script every time.
Any dependencies available from packages.debian.org would be installed normally in TemplateBasedVM to speed up above a bit so only the package/software missing from packages.debian.org gets installed over and over again in TemplateBasedVM.
Nice work 0brand on information leaks and the printing and scanning page.
BTW (re: that other thread on hostnames) - just to clarify explicitly for the wiki, the hostname that is visible is “user” for all Whonix users? Including Qubes?
Qubes logs show “Set hostname to host”. I also thought somewhere else in logs it sets it to “none” in Qubes.
Trying to error on the side of caution. My thinking was.