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

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

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

The GitHub Continuous Integration checks passed OK.

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

Also, I noticed on https://rpki-client.org that it still references 9.3, even though the URL linked to by the "rpki-client 9.3" text is the release announcement for 9.4.

I'm prepping a submission for undeadly.org as well, but I thought I would let you know about that version number typo on the website in the meantime.

Thank you for the continued improvements!

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

#OpenBGPD 8.6 has been released, which will be arriving in the OpenBGPD directory of your local #OpenBSD mirror soon. #BGP

Tip of the Week: When using #OpenBGPD and using loopbacks on neighbors distributed via OSPF, you'll need the nexthop qualify via bgp global option or your table won't move to a valid state if there is a route in there required for next hop.

On Cisco IOS, all protections are off, so nothing needed in that space.