shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

245
active users

#LetsEncrypt

5 posts4 participants3 posts today

Install and Configure #Cacti on #AlmaLinux #VPS This article provides a guide demonstrating how to install and configure Cacti on AlmaLinux VPS.

What Is Cacti?
Cacti is an open-source network monitoring and graphing tool built on top of RRDtool. It’s designed to collect, store, and visualize time-series data from networks and systems.
What Cacti Does

Polls data from devices ...
Continued 👉 blog.radwebhosting.com/install #mariadb #selfhosted #opensource #letsencrypt #selfhosting #rrdtool

Install and Configure Cacti on AlmaLinux VPS
RadWeb, LLC · Install And Configure Cacti On AlmaLinux VPS - VPS Hosting Blog | Dedicated Servers | Reseller HostingThis article provides a guide demonstrating how to install and configure Cacti on AlmaLinux VPS.

My current conspiracy theory: Now that #letsencrypt has more or less destroyed the market for domain certificates and people are more interested in using client/user certificate, Google throws the market a lifeline by removing clientAuth from acceptable certificates in the browser context with some vague "it's about security" arm waving. #NerdTalk

1/4

Remember the threads¹² about #LetsEncrypt removing a crucial key usage from certificates issued by them in predictive obedience to their premium sponsor Google?

We were at first concerned about #SMTP. While I had lived through this problem with #StartSSL by #StartCom back in 2011, I only had a vague recollection of Jabber but recalled in detail that it broke server-to-server SMTP verification (whether the receiving server acted on it or just documented it).

Well, turns out someone now reported that it indeed breaks #XMPP entirely: https://community.letsencrypt.org/t/do-not-remove-tls-client-auth-eku/237427/66

This means that it will soon no longer be possible at all to operate Jabber (XMPP) servers because the servers use the operating system’s CA certificate bundle for verification, which generally follows the major browsers’ root stores, which has requirements from the CA/Browser forum who apparently don’t care about anything else than the webbrowser, and so no CA whose root certificate is in that store will be allowed to issue certificates suitable for Jabber/XMPP server-to-server communication while these CAs are the only ones trusted by those servers.

So, yes, Google’s requirement change is after all breaking Jabber entirely. Ein Schelm, wer Böses dabei denkt.

While https://nerdcert.eu/ by @jwildeboer would in theory help, it’s not existent yet, and there’s not just the question of when it will be included in operating systems’ root CA stores but whether it will be included in them at all.

Google’s policy has no listed contact point, and the CA/B forum isn’t something mere mortals can complain to, so I’d appreciate if someone who can, and who has significant skills to argument this in English and is willing to, to bring it to them.

① mine: https://toot.mirbsd.org/@mirabilos/statuses/01JV8MDA4P895KK6F91SV7WET8
② jwildeboer’s: https://social.wildeboer.net/@jwildeboer/114516238307785904

Let's Encrypt Community Support · Do *NOT* remove TLS Client Auth EKU!I was also bit by this. I switched to tlsserver profile, and when my XMPP certificate got renewed today, it failed to make any S2S connections :(. I'd to revert to classic profile. Could we please keep TLS client auth EKU ? Thanks!

yet another ACME client, based on uacme: github.com/llfw/lfacme

good:
+ uses uacme and POSIX /bin/sh
+ better configuration/hook system than dehydrated
+ comes with manpages
+ small and simple
+ supports Kerberized dns-01 domain validation

bad:
- only tested on FreeBSD (but this could be improved)

(edit: now supports http-01 challenges!)

/cc @_bapt_

a simple ACME client based on uacme. Contribute to llfw/lfacme development by creating an account on GitHub.
GitHubGitHub - llfw/lfacme: a simple ACME client based on uacmea simple ACME client based on uacme. Contribute to llfw/lfacme development by creating an account on GitHub.

Just requested that Auto Encrypt¹ is added to the list of @letsencrypt clients for Node.js and that Kitten² is added to the list of projects that integrate Let’s Encrypt support:

github.com/letsencrypt/website
github.com/letsencrypt/website

I originally requested that Auto Encrypt and Site.js (the precursor to Kitten, now sunset) be added to the list in 2021. It was not approved (no reason given), so hopefully this time will be different.

github.com/letsencrypt/website

¹ codeberg.org/small-tech/auto-e
² kitten.small-web.org

Automatically provisions and renews Let’s Encrypt TLS certificates on Node.js https servers (including Kitten, Polka, Express.js, etc.)
Implements the subset of RFC 8555 – Automatic Certificate Man...
GitHubAdd Auto Encrypt to clients.json by aral · Pull Request #1921 · letsencrypt/websiteBy aral

🔒 Auto Encrypt – heads up!

In the next minor version release of Auto Encrypt¹, we’ll be moving from a hard-coded date-based certificate renewal check to using ACME Renewal Information (ARI)².

The change³ should be seamless.

If you have any concerns, now is the time to raise them :)

#AutoEncrypt #TLS #LetsEncrypt #SmallTech #SmallWeb

¹ Drop-in Node.js https server replacement that automatically provisions and renews Let’s Encrypt certificates for you. (codeberg.org/small-tech/auto-e)
² datatracker.ietf.org/doc/draft
³ codeberg.org/small-tech/auto-e

Summary card of repository small-tech/auto-encrypt
Codeberg.orgauto-encryptAutomatically-provisioned TLS certificates for Node.js servers using Let’s Encrypt.
Replied to Jan Wildeboer 😷:krulorange:

@jwildeboer wrote:
"Dear #Letsencrypt, you helped secure millions and millions of servers"

They never did. Since Forward Secrecy is used (which is good), the one and only purpose of an X.509 certificate is to authenticate an entity, based on unique and *useful* identification of said entity.

Have a look at crt.sh/?q=968717.com for the "usefulness" of identification (and waste of resouces).

Or what about crt.sh/?q=localbit.com which includes certificates for ww25.ww38.ww38.ww38.ww16.ww25.? (I can give you zillions of examples like this).

Although a DV-cert may suffice for server to server communication (*), a domain name simply does not suffice for useful identification by humans.

Fix: infosec.exchange/@ErikvanStrat.

(*) Certificate misissuances: infosec.exchange/@ErikvanStrat.

crt.shcrt.sh | 968717.comFree CT Log Certificate Search Tool from Sectigo (formerly Comodo CA)
Continued thread

Sure, #LetsEncrypt, you can say that using certificates with the ClientAuth UKE is a minor use case and that this functionality was never guaranteed to always be available and all of that. But the fact stays: you are removing a feature from your certificates that has been here for a very long time, just because Google demands this. Why Google wants this? I will ask them. But I am quite sure that this #oopsie side effect is not an oversight.

3/5

I am totally sure (sarcasm included) that #Google has totally overseen that their planned changes to their root program requirements will cause a lot of problems for mailserver owners like me who in future might run into weird problems with #Letsencrypt certificates for SMTP. I am sure that Google is absolutely not trying to make running your own mailserver even more complicated just to protect their gmail business. That would be totally not how Google thinks, amirite? letsencrypt.org/2025/05/14/end

What the actual fuck, #LetsEncrypt

Let’s Encrypt will no longer include the “TLS Client Authentication” Extended Key Usage (EKU) in our certificates beginning in 2026.

That makes them unusable for SMTP servers. Gah!

Anyone got a usable alternative that doesn’t ruin financially?

Update: I’m in communication with them, let’s hope they recognise the usefulness.