It is generally accepted that the infrastructure should not be trusted and using any resources unnecessarily to shore up infrastructure would be a waste of time. qubes.os FAQ applies here.,
Should I trust this website?
This website is hosted on GitHub Pages (why?). Therefore, it is largely outside of our control. We don’t consider this a problem, however, since we explicitly distrust the infrastructure. For this reason, we don’t think that anyone should place undue trust in the live version of this site on the Web. Instead, if you want to obtain your own, trustworthy copy of this website in a secure way, you should clone our website repo, verify the PGP signatures on the commits and/or tags (signed by the doc-signing keys), then either render the site on your local machine or simply read the source, the vast majority of which was intentionally written in Markdown so as to be readable as plain text for this very reason. We’ve gone to special effort to set all of this up so that no one has to trust the infrastructure and so that the contents of this website are maximally available and accessible.
What does it mean to “distrust the infrastructure”?
A core tenet of the Qubes philosophy is “distrust the infrastructure,” where “the infrastructure” refers to things like hosting providers, CDNs, DNS services, package repositories, email servers, PGP keyservers, etc. As a project, we focus on securing endpoints instead of attempting to secure “the middle” (i.e., the infrastructure), since one of our primary goals is to free users from being forced to entrust their security to unknown third parties. Instead, our aim is for users to be required to trust as few entities as possible (ideally, only themselves and any known persons whom they voluntarily decide to trust).
Users can never fully control all the infrastructure they rely upon, and they can never fully trust all the entities who do control it. Therefore, we believe the best solution is not to attempt to make the infrastructure trustworthy, but instead to concentrate on solutions that obviate the need to do so. We believe that many attempts to make the infrastructure appear trustworthy actually provide only the illusion of security and are ultimately a disservice to real users. Since we don’t want to encourage or endorse this, we make our distrust of the infrastructure explicit.
Why do you use GitHub? (Could be changed to “Why use Discourse?”)
Three main reasons:
- We distrust the infrastructure, including GitHub (though there are aspects we’re still working on).
- It’s free (as in beer). We’d have to spend either time or money to implement a solution ourselves or pay someone to do so, and we can’t spare either one right now.
- It has low admin/overhead requirements, which is very important, given how little time we have to spare.
Admin/overhead of Discourse (is ?) vs. What forum software did you say has lower Admin/overhead? better security? Works with onions? Will not have any/other problems not currently experienced on whonix.org?
A knee jerk reaction would be so assume that none of your concerns have been brought up or considered before. But just like everyone else you claim to have the answer but aren’t will to help move whonix.org in that direction. For starters this might include
- Finding suitable forum software to migrate to. Meaning requires low resources, low admin overhead. Tor/.onion compatible, no Java Scirpt…
- Testing this platform for whonix developers/sysadmin
Everyday whonix deveopers have countless ideas brought to them by the good idea fairy but no one is willing to lift a finger to help. So my question:
If this i so important to you what would you be willing to do to make it happen. I mean if I want something done on whonix.org I have to take the initiative Although a very corny and cliche, “Talk is cheap actions speak” applies here.