home tags events about rss login

Things happen.

horia honked 21 Mar 2023 20:01 -0700

"Only four Canadians in a heck of a long time!" --Theo de Raadt

horia honked 21 Mar 2023 19:33 -0700

"I encourage OpenBSD users to be Canadian" --Katie McMillan

horia honked 17 Mar 2023 12:58 -0700

Happy Saint Patrick's Day!

Happy Saint Patrick's Day!

horia honked 17 Mar 2023 11:02 -0700

@tedu after honk upgrade on v0.9.9, adding or removing honkers "can't get honker xid: sql: no rows in result set"

horia bonked 17 Mar 2023 08:13 -0700
original: tedu@honk.tedunangst.com

#honk 0.9.9 "Eat the Bugs" is released.

It fixes a bunch of stuff. It's a few weeks late because I kept fixing stuff, but that'll never end, so here it is. We've run out of version numbers before 1.0 unless we resort to numerative easing, so this may be your last chance to earn an exclusive beta tester nft.

Thanks to everyone who helped out.

horia bonked 16 Mar 2023 08:25 -0700
original: stsp@bsd.network

The nsh ("network shell") 1.1 release has been tagged.

https://www.nmedia.net/nsh/

A website update is still pending but there is a preliminary change log for the 1.1 release at
https://github.com/yellowman/nsh/releases/tag/v1.1

A number of contributions from me made it into this release with support from @ogmaconnect, focusing on compatibility with #OpenBSD 7.3 and usability improvements

I am excited about where this is headed: We will continue pushing forward the nsh project's vision of providing a fully-featured OpenBSD administration interface which is accessible to people who have been trained on commercial networking gear from various well-known vendors. People other than those who already have the self-taught Unix skills required to configure and maintain OpenBSD-based firewalls and routers.

If this sounds interesting to you then please try nsh and let us know what features you see lacking in the current implementation. We would be happy to receive feedback and learn more about what is needed to fill the gaps.

To install nsh on OpenBSD, run: pkg_add nsh

horia bonked 16 Mar 2023 07:50 -0700
original: tedu@honk.tedunangst.com

A little update on the temperamental mastodon, signed fetch, etc. This gets a bit confusing and goes off into the weeds, but maybe it's interesting if you're into fediverse nitty gritty.

For background, I have trouble federating with mastodon in "secure" mode (I have signed fetch turned off). In theory, and I think according to most people's expectations, this would mean I can't talk to the secure servers. In reality, that basically works fine, but it's the secure servers that can't talk to me. Except sometimes.

As previously noted, I am intermittently able to retrieve the signing key with an anonymous get. But usually not. If I'm following somebody on such a server, I get a whole pile of error messages in the log, and generally do the courteous thing and unfollow to spare their server some load. But I don't have to unfollow everybody...

For example, I used to follow Alejandro and Beatrice, on the same temperamental server. Beatrice posts a lot, but I was unable to get her key, had a bunch of failures, and unfollowed. I didn't unfollow Alejandro because the server was happy and served up the key.

Time passes, and now I can't get Alejandro's key anymore, but I did get Beatrice's key. Only the great Ganesha knows why. But because mastodon will send replies to followers (if it's the same server), I now see Beatrice's replies to Alejandro, but I can't see the original, even though I'm following A and not B. Awesome, right?

Anyway, there's not really a point, just another day on the fediverse. Pound sign annals of activitypub.

horia bonked 16 Mar 2023 07:41 -0700
original: reyk@mastodon.social

Back in 2017, I had a PoC to integrate machine learning into our Esdenera firewall product. We already used LuaJIT for our AppID implementation inside the privilege-separated appid, so it wasn’t too difficult to integrate the original torch.ch. The challenge was building and training the model, of course, but we had a collaboration with the local university and public funding for the project. The downside: it was barely enough to finance the team so I couldn’t make it a priority. 1/2