Shawn WebbCurrent status: Setting up a #Tor Onion Service for the new #HardenedBSD pkgbase repos.
I've added some basic instructions on accessing #HardenedBSD resources (package repos and OS binary updates) over #Tor here: https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/wikis/home#accessing-hardenedbsd-resources-through-tor
I think some refinements could be made, but this is at least an initial draft. If anyone has any ideas for further refinement, please let me know.
ClaritrieClaritrie just launched! 🌍✨
Site: claritrie.com
It is a debate platform where an AI curator organizes discussions using Argument Maps—ensuring transparency, fairness, and deeper conversations.
This isn't just another forum—it's a step toward structured, meaningful discourse where ideas, not algorithms, shape the conversation.
Join me in shaping the future of debate and human rights online!
#DebatePlatform #AIforGood #HumanRightsTech #EthicalAI #OpenDiscussion
Getting the lab side of my home office organized for mesh network R&D. Here we see four Protectli FW4B devices that will serve as the reference implementation.
This is where the @radicle project gets it right.
The #Radicle development team has done a fantastic job at supporting different methods of network access, including explicit support for the ways #Tor might be configured in the operating environment.
I can rest assured that Radicle can be safely deployed in any environment.
Forcing all public Internet traffic to go through #Tor via a transparent proxy, certain open source projects will need to remove their prohibition on resolving .onion names.
Transparent proxying opens up the possibility of completely oblivious Tor Onion Service support.
Open source libraries and applications need to permit .onion domain queries by default.
For projects that want to prohibit .onion by default, I would suggest this:
Don't. Provide a facility wherein the end user can optionally block resolution of any TLD or hostname.
For example, one could envision a user wamtomg tp block the .zip TLD. Or another user desiring to block the .onion TLD.
The decision should be left by the user as to what to permit or prohibit.
HardenedBSDThe #HardenedBSD Foundation and The HardenedBSD Project are happy to announce a collaboration with #Protectli to research and develop a censorship- and surveillance-resistant mesh network: https://hardenedbsd.org/article/shawn-webb/2024-09-23/hardenedbsd-and-protectli-collaborates-censorship-and-surveillance
Here we see a hardware donation from the fine folks at #Protectli. They have donated 4xFW4B devices to support our next foray into #HumanRightsTech.
Early in 2025, the #HardenedBSD project plans to put in a concerted effort at developing a censorship- and surveillance-resistant mesh network.
More details will come in a future official announcement from the HardenedBSD project.
The #Radicle project is a shining example of how to properly support #Tor. They even have a guide on how to use Radicle within a fully Tor-ified network: https://radicle.xyz/guides/user/#4-embracing-the-onion
Would be very cool to see a #HardenedBSD port of this by the community: https://securedrop.org/news/securedrop-workstation-1_0_0-released/
SecureDrop Workstation 1.0.0 Released
SecureDrop Workstation 1.0.0 has been released! This is the first release targeting Qubes 4.2 and will require a full reinstall. With 1.0.0, we’re now switching to an open beta: if you are interested in using SecureDrop Workstation, please reach out to us!