photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

247
active users

#letsencrypt

3 posts3 participants0 posts today

UPDATE: Thx to the replies, I implemented the change for all my domains, did a `certbot renew --dry-run` and that succeeded. Yay to a cleaner config :)

#NerdQuestion. When I move {server [...] } blocks in `/etc/nginx/nginx.conf` to separate files in the `/etc/nginx/conf.d` directory, will certbot still find them and will automatic renewals just keep working as before? Anyone with experience on that?

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.

Dinge um die ich als IT Entscheidender einen großen Bogen mache:

- #broadcom
- #hp
- #lenovo
- #lancom
- Eigene #mailserver
- Telefonanlagen-Dienstleister
- proprietäre Security (Firewall, SIEM, etc.)
- Windows (sofern Möglich)
- #office365 (oder wie auch immer das diese Woche heißt)
- #sap
- Datenverarbeitung auf Android
- Port Forwards
- #docker
- Cloud/SaaS Dienste
- Tageslicht
- GData, Symantec etc.
- GoDaddy und Co.
- Zertifikate zum Kauf #letsencrypt ❤️

Wie sieht eure Liste so aus?

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.

New Kitten Release 🥳

To OCSP¹ or not to OCSP…

• Turns on OCSP support in the server only if the site’s certificate has the OCSP stapling extension.

This is to support both servers that still have OCSP stapling in their certs as well as new ones that don’t. (Let’s Encrypt sunset OCSP support yesterday and there is a transitionary period where Kitten servers will have both types of certificates. This update is to ensure we support both without issues.)

kitten.small-web.org

Also updated, if you’re interested in playing lower in the stack:

• @small-tech/https: codeberg.org/small-tech/https
• @small-tech/auto-encrypt: codeberg.org/small-tech/auto-e

Enjoy!
:kitten:💕

¹ Online Certificate Status Protocol (en.wikipedia.org/wiki/Online_C). Yes, I hate abbreviations too :)

kitten.small-web.orgKitten: Home