HardenedBSD Officially Migrated to Radicle

[Shawn Webb]

Hey all,

Over the past week, I have been working on bringing HardenedBSD's code
repositories on Radicle (as most/all of you already know by now.) We are now at
the point where Radicle is usable for us. There are still some sharp edges and
some things to work out, but the core functionality is working.

I have done some very basic/naive integration in the ports tree for downloading
project distfiles from a radicle-httpd instance, similar in scope to
USE_GITHUB/USE_GITLAB. This integration still needs a lot of work, but it works
well enough to build ports-mgmt/pkg.

Radicle does still have some issues with regards to performance. You will want
to configure Radicle explicitly to support larger repos. You may need to edit
the Radicle config at ~/.radicle/config.json and set the
node.limits.fetchPackReceive setting to at least 3GB.

You can browse our repos at: https://radicle.network/nodes/rad.hardenedbsd.org

Here are our current repos. I plan to migrate 100% of our repos over time.
secadm will likely be next.

1. rad:z2HLHXgL1xevBNQsf8BmQW7MpJmtm: HardenedBSD-src
2. rad:z2XrdvALg77ycnuZRXgScb27yb3wM: HardenedBSD-ports
3. rad:z3QDZAW2FAfuLvihrhiyDC9fAD8G9: HardenedBSD-pkg

These are the steps I've found to be the most reliable:

1. Connect to the HardenedBSD seed vm:
rad node connect z6MknwwMpmZET1PcvQjPYhA6...@rad.hardenedbsd.org:8776
2. Seed the src tree (repeat for ports):
rad seed --from z6MknwwMpmZET1PcvQjPYhA6hGY7wkYzxb9YtSRh5j2qSQdG rad:z2HLHXgL1xevBNQsf8BmQW7MpJmtm
3. Watch ~/.radicle/storage/rad:z2HLHXgL1xevBNQsf8BmQW7MpJmtm.tmp to move to
~/.radicle/storage/rad:z2HLHXgL1xevBNQsf8BmQW7MpJmtm. When this happens, you now
have the src tree stored in Radicle's local storage. This will take a long
while. Grab a pizza and a root beer.
4. Clone the repo: rad clone rad:z2HLHXgL1xevBNQsf8BmQW7MpJmtm

Thank you everyone for your patience, support, and help. This has been a rather
wild ride (and it's technically not over). As I make progress on further Radicle
integration, I will keep everyone informed.

Thanks,

--
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Signal Username: shawn_webb.74
Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc

[Shawn Webb]

I just learned that running a Radicle node is not required for
cloning/puliing our repos.

Users can just use git like normal, but pointing their remotes to the
Radicle web instance. Here's an example of how to clone our src tree:

$ git clone \
https://rad.hardenedbsd.org/z2HLHXgL1xevBNQsf8BmQW7MpJmtm.git \
HardenedBSD-src

Rinse and repeat for all the repos users might be interested on our
Radicle web instance:
https://radicle.network/nodes/rad.hardenedbsd.org

The only downside is that users who use this method will not be able
to open issues or submit patches. Those two tasks require running a
Radicle node locally.