I submitted a Pull Request to update MacPorts' rpki-client to 9.7 here:

https://github.com/macports/macports-ports/pull/30763

GitHub's Continuous Integration checks passed!

It's up to someone else with commit access to merge it.

For whatever reason? The rpki-client.org website main page hasn't been updated to reflect the release of 9.7 yet, but it's there on the mirrors (and I verified the tarball with signify) and an undeadly.org story was posted, so I am guessing I didn't really beat anything to the punch so much as the World Wide Web isn't a first class citizen contrasted with those toiling in the realms of securing routing protocols, as it should be.

#RPKI #rpkiclient #MacPorts #OpenBSD #OpenBGPD #BGP #OpenSource

OpenBGPD 9.0 released https://www.undeadly.org/cgi?action=article;sid=20251231070524 #openbsd #openbgpd #bgp #routing #networking #opensource #libresoftware #freesoftware #bsd

OpenBGPD 8.9 released https://www.undeadly.org/cgi?action=article;sid=20250926141610 #openbsd #openbgpd #bgp #routing #networking #security #freesoftware #libresoftware

@stefano Hey! How are you doing man? Are you currently doing anything with #OpenBGPD?

#OpenBSD 7.7 has been released (#BSD / #NetBSD / #386BSD / #Unix / #LibreSSL / #OpenSSH / #OpenBGPD / #OpenSMTPD / #OpenNTPD / #OpenIKED / #rpkiClient / #mandoc) https://openbsd.org/

I submitted a Pull Request to update MacPorts' rpki-client to 9.5 here:

https://github.com/macports/macports-ports/pull/28128

GitHub Continuous Integration checks passed!

Update: Or at least I thought they did?

Now seeing this error:

"Creating port index in /Users/runner/work/macports-ports1597/macports-ports1597/ports
Adding port net/rpki-client
signal interp lost
ports/.github/workflows/bootstrap.sh: line 150: 2047 Abort trap: 6 portindex -e
Error: Process completed with exit code 134."

o.O

From: https://github.com/artkiver/macports-ports1597/actions/runs/14437970476

Even though previously in the GitHub UI, it showed all three checks as green. wtfh? I mean, I hate GitHub and have less than no reason to trust it, but that's a new one, even for me.

If I check: https://github.com/macports/macports-ports/pull/28128/checks

All is green there too. I am so confused.

Regardless, it's up to someone else with commit access to merge it.

Meanwhile, still no assistance regarding my request for help on the MacPorts' patches for OpenSSH 10.0p1/2 for ssh-agent.c and sshd-session.c, but someone else did open another Trac issue regarding OpenSSH's logging (or lack thereof) here:

https://trac.macports.org/ticket/72345

Though, they also observe the same behavior with the Apple shipped version, so they pontificate if it may be an issue upstream?

Ya think?

Sometimes, I think folks vastly overestimate what "maintainer" means or how much I might be using some of this software or what they expect me to do about it just because it is "assigned" to me.

For example: I basically do not run sshd on any macOS systems, since I only have Apple laptops which sleep a lot and are absolutely awful as anything that should be a server running daemonized software.

Did these folks not notice that Apple themselves discontinued their XServe hardware line circa 2004? Or that even their "OS X Server" product was discontinued from the App Store in 2022?

I guess they missed the memos, couldn't read the room or writing on the wall?

But then, they observed this in macOS Monterey, which itself is from 2021, so maybe they just prefer livin in the past? I have no idea.

I am not even sure how to meaningfully reply to that Trac issue.

#RPKI #rpkiーclient #MacPorts #macOS #BGP #OpenBGPD #OpenSource

OpenBGPD 8.8 released https://www.undeadly.org/cgi?action=article;sid=20250207192657 #openbgpd #openbsd #routing #bgp #networking

OpenBGPD 8.7 released https://www.undeadly.org/cgi?action=article;sid=20241218195732 #openbsd #openbgpd #bgp #routing #security #networking #freesoftware #libresoftware #bsd