Indeed. It may or may not be remotely fingerprintable but consider the user is prefering this font in non-anonymous and anonymous VMs then reduces anonymity set by posting screenshots with support requests for both. In either case, for an abundance of caution it is best avoided to even avoid the question.
Now that kicksecure.com is online, there are two recommended host operating systems for Whonix:
While migrating Disable TCP and ICMP Timestamps - Whonix to Kicksecure wiki I was wondering what to do with instructions on how to disable TCP and ICMP timestamps on other Linux such as Debian, MacOS and Windows. I think keeping this documentation is too much and should be rejected. If someone wants better security like an operating system that disabled TCP and ICMP timestamps by default, use either Kicksecure or Qubes OS as a host operaging system.
Documenting the same for Debian, MacOS, Windows and even OpenBSD is stretching the project focus too thin. It’s a bit similar like the Debian wiki explaining how to do something on Windows or the MacOS website explaining how to do something on Debian.
The only documentation on Windows, MacOS will be how to install VirtualBox and import Whonix. That is useful to first time Linux users to try out Whonix but for better security these host operating systems are a lost cause. Instructions how to disable TCP and ICMP timestamps would be incomplete in the bigger picture since there would be a lot more host security settings (such as disabling telemetry) that should’t be part of Whonix wiki. Becuase the other way around, we’d also have to host full instructions on how to harden a Windows or MacOS host operating system which would be huge.
Re: kicksecure wiki & existing documentation on Whonix website.
I don’t agree wtih the principle re: removing wiki pages on Whonix that are common to both and redirecting readers to the other website:
Readers often don’t read the existing documentation on whonix.org as it stands (just look at forum posts re: people often asking basic questions that are already answered in docs i.e. haven’t done their homework). Splitting across two websites will just increase that problem.
Better IMO to have one “complete” set of documentation in one place for simplicity and as a definitive security and privacy guide.
The kicksecure site can remain very simple and just get occasional page updates to match whonix.org documentation as required i.e. focused on security as you pointed out.
The vast majority of the user population is likely to remain focused on Whonix for many years to come → kicksecure is a novelty at present that is unlikely to have a large, standalone user base.
Whonix is well known, but the kicksecure base not so much.
On that basis, I would reject those suggested edits that is redirecting certain pages to kicksecure.com
Sure - will have a look.
Also, re: Kicksecure logo.
I like the last two:
Small padlock with full text; or
Just the wording with the nice, weird “K”
If I had to choose, probably #1.
Will get to other recent, suggested edits when I have a chance. Christmas time is busy…
For many it’s “issue → ask somewhere”. I don’t think it would make a difference.
Problem is, there are ~ 70 repositories on gitlab.com/whonix. Security / anonymity all mixed up. The security parts cannot get as much outside attention if mixed up with anonymity. By a clean separation of projects, I hope things will look less daunting and easier to grasp.
Documentation in Whonix wiki would be complete because Whonix /wiki/Documentation would continue to have a complete overview even some links are to an external website, i.e. Kicksecure wiki.
Lots of duplication for things which are the same for Kicksecure and Whonix
Hard to keep track of backporting improvements from one wiki to the other wiki, especially if both versions have been edited independently
Occasional page updates in the KIcksecure would be harder than one might imagine. Many Whonix wiki pages are 95-99% unspecific to anonymity and about security only. But the remaining 1-5% anonymity specific content would make these pages unfit for unmodified copy/paste into Kicksecure wiki.
By not filling up Kicksecure wiki with relevant documentation for users and security features developer documentation, restricting the project to have minimal documentation, would be kinda maintaining the project with handbrakes on.
I am expecting the Kicksecure user base to exceed the Whonix user base since it’s simpler to use, no VMs required, the computer security enthusiasts community being a magnitude bigger than the anonymity enthusiasts community, no slow browsing speeds and all the anonymity knowledge not required.
Unfortunately these edits are ongoing and already done according to my instructions for 3 weeks.
No more need to add links (onion). Easy to illustrate the alternative onion link by using the new link template. There are no longer extraneous links to the web archive for onion links (which would be broken since web archive does not support onion links).
Due to issues with MediaWiki skin foreground (Broken with mw 1.37), we’re back to MediaWiki default skin Vector and CSS enhancements are being added on top of it.
All enhancements to MediaWiki in the Whonix wiki are being documented here: