Hi Rob, Thanks for the offer. I fear that most of the complexity lies in code and not so much in system administration.
The existing code-base depends on outdated forks of old projects, which prove hard to be brought back up to speed. Without having much understanding of the code, I've tried updating things in https://github.com/xmpp-observatory/xmppoke/pull/11 but that wasn't successful. A warning banner has been placed on the existing website, and plans for a replacement service are materializing. Kind regard, Guus On Wed, Feb 2, 2022 at 1:25 AM Rob Loranger <[email protected]> wrote: > Guus, > > What kind of maintenance is needed? I might be able to spare some system > admin time. > > - Rob > On 2022-02-01 01:05, Guus der Kinderen wrote: > > Hi Bruce, > > I'm afraid that there's a lack of people available to do maintenance to > that service (it has other issues besides that LE root) There has been some > debate on replacing it completely. I'm wondering if it'd be better to > switch of the now largely misbehaving service until a fix or replacement > can be put in place. > > Regards, > > Guus > > On Tue, Feb 1, 2022 at 4:29 AM Bruce Walzer <[email protected]> wrote: > >> This is the post on the OpenBSD subreddit that prompted this list post: >> >> * >> https://old.reddit.com/r/openbsd/comments/shgdp0/xmppserver_with_openbsd_prosody_someone_getting_a/ >> >> It appears that whatever the IM Observatory is using for TLS root >> certificates was not been updated to accommodate the root certificate >> expiry that Let's Encrypt experienced at the end of September. For >> example, OpenBSD keeps such root certificates in /etc/ssl/cert.pem and >> failure to update this file causes current Let's Encrypt TLS >> certificates to fail. >> >> Thanks! >> >
