Current status: Setting up a #Tor Onion Service for the new #HardenedBSD pkgbase repos.
#HumanRightsTech
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.
Claritrie 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.
The #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/
Here we see two #Radicle seed nodes, running behind my fully Tor-fied network.
This is a test of exposing a Radicle seed node as a Tor Onion Service endpoint.
These two Radicle nodes are deployed on a #HardenedBSD 14-STABLE VM.
Huge step forward for #HumanRightsTech.
For more information on Radicle (a sovereign {code forge} built on Git): https://radicle.xyz/
Huge shout-out to the Radicle dev team for this collaboration. It has been a blast working with them.
Current status: Deploying a test #Radicle node on #HardenedBSD. Going to seed the HardenedBSD src and ports repos.
I'm hoping to continue expanding alternative forms of access to our resources (both code and infrastructure).
If this test proves successful, we may have another official method of getting HardenedBSD-related stuffs.
I'll be giving a presentation on #HardenedBSD today in Denver, Colorado at 6:30pm. If you're interested in #FreeBSD, #infosec, and/or #HumanRightsTech, I'd love for you to come join me.
Initial work on removing the prohibition of .onion in #libcurl in favor of a user-provided DNS blocklist approach: https://git.hardenedbsd.org/shawn.webb/curl/-/commit/270380bdc3505db03780382833fabf7775c9683b
Some follow-up work to be done, but this initial commit works.
I've now applied the patch to the ftp/libcurl port in the #HardenedBSD ports tree: https://git.hardenedbsd.org/hardenedbsd/ports/-/commit/3173d64b4bc01c0c1c258fe5191c65ea0a766181
To developers working in networking code: please just do the right thing: do not treat any TLD as special. Do not violate the principle of least astonishment, especially when it comes to DNS.
Perhaps we can convince the #curl #libcurl community to revert the patch on their end.
Got my fully Tor-ified home network set up again. Now I can fully test the #HardenedBSD #Tor Onion Service endpoints.
The question I have about #Veilid:
Can I serve the #HardenedBSD package repos and binary update artifacts over Veilid like I can (and do) via #Tor onion service?
My next #HardenedBSD infrastructure goal is to provide a #Tor Onion Service endpoint for this #Vaultwarden instance.
I'm unsure how well, if at all, websockets work behind Tor.
The core #HardenedBSD dev/build infrastructure is now back online!
The next task is to get our #Tor Onion Service nodes back online. That'll be a task either for later tonight or tomorrow.
I've now updated the #HardenedBSD #Tor Onion Service endpoints to
point to the new build infrastructure bits. Users can now deploy
HardenedBSD completely through Tor, including git clone, the
installation media, packages, etc.
Users can go from zero to dev to prod and everything inbetween
completely through Tor.
#TorProject #HumanRights #HumanRightsTech #HumanRightsInfrastructure
#infosec #FreeBSD
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst