Recent searches

No recent searches

Search options

Only available when logged in.
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:

269
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#acme

0 posts0 participants0 posts today
Stéphane Bortzmeyer

Si vous utilisez #LetsEncrypt, vous avez sans doute reçu les messages « Let's Encrypt Expiration Emails Update » qui vous préviennent que cette AC n'enverra plus de rappels que vos certificats vont bientôt expirer. C'est parce qu'un meilleur système est maintenant disponible, #ARI.
ARI permet à une AC utilisant le protocole #ACME d'indiquer à ses clients des suggestions sur le renouvellement des certificats. Il est décrit dans ce #RFC.

bortzmeyer.org/9773.html

www.bortzmeyer.orgBlog Stéphane Bortzmeyer: RFC 9773: ACME Renewal Information (ARI) Extension
*
ivy

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_

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.
#freebsd#letsencrypt#acme
Aral Balkan

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

GitHubAdd Auto Encrypt to clients.json by aral · Pull Request #1921 · letsencrypt/websiteBy aral
#SmallWeb#SmallTech#AutoEncrypt
Quixoticgeek

Does anyone know how this new SSL cert expiry date thing is going to affect things like user authentication with SSL certs, i.e. for openvpn.

If we're running our own CA, can I get safari, chrome et al to accept longer cert expiry?

#Linux#SSL#OpenVPN
Aral Balkan

So after listening to your feedback, I agree: let’s spend that money in the EU to create a publicly-owned, free and open ACME-compatible certificate authority.

See post quoted below, with links to Tom’s work as he’s already been thinking/working on this.

#EU #ACME #TLS #security #LetsEncrypt #technologyCommons #SmallTech mamot.fr/@tdelmas/114224564125

Mamot - Le Mastodon de La Quadrature du Net Tom (@tdelmas@mamot.fr)@aral@mastodon.ar.al Or let's use the protocol they created - ACME - to create more independent CA, EU-based ! https://github.com/tdelmas/Let-s-Clone
DrScriptt

I started a discussion with fellow #sysadmin about updating #BIND / #named config to migrate from the overly permissive allow-update {…} stanzas to the more restricted update-policy {…} stanzas using targeted grant statements.

The idea being to allow the #acme client to only be able to update (add / delete) _acme-challenge TXT instead of any record in the zone.

Old:

allow-update {
TSIG_KEY_NAME;
};

New:

update-policy {
grant TSIG_KEY_NAME name _acme-challenge.example.net TXT;
};

#acmesh#certbot
TrendingLive feeds
About