Hallo liebe Technikmenschen :) Die Mail von let's encrypt sagt ja recht deutlich, daß der momentan verwendete Client ein Update braucht. Ich würde dafür gerne den Menschen mit entsprechenden Rechten auf dem System das Skript https://github.com/srvrco/getssl empfehlen. Pros: * rein bash basiert, kein binary blob, der am Paketmanagment vorbei installiert wird (afaik mit Stand von vor 3 Jahren) * Multi Domain fähig, also das eine Skript kümmert sich um protokolle.zapf.in, mumble.zapf.in usw. * einfache Bedienung; toll fand ich, das ein Kommando reicht, um ein Zertifikat für eine neue Subdomain einzurichten * das Skript überprüft per cron, ob ein Zertifikat erneuert werden muss und macht das gegebenenfalls (und rechtzeitig!) * niemand beschwert sich wieder über ein abgelaufenes Skript, was eh "immer" dann passiert, wenn man keinen Kopf für den Kram hat * auf Wunsch per Fernzugriff LG Jörg (Siegen) Am 3. März 2021 13:15:19 MEZ schrieb noreply(a)letsencrypt.org: >Hi, > >According to our records, your Let's Encrypt software client renewed a >TLS/SSL certificate recently using the ACMEv1 protocol. Here are the >details >of one recent ACMEv1 request from each of your account(s): > >Client IP address: 2a01:238:4387:cc00:1027:fc0d:cfe6:c387 > >User agent: CertbotACMEClient/0.17.0 (certbot; Debian GNU/Linux 8 >(jessie)) Authenticator/webroot Installer/None (renew; flags: n) >Py/2.7.9 > >Hostname(s): "protokolle.zapf.in" > >Request time: 2021-02-22 11:45:51 UTC > >On June 1, 2021, you will no longer be able to renew your certificates >using >ACMEv1. You should upgrade to an ACMEv2 compatible client before June >1, or >certificate issuance will fail. Until then, we will also have >occasional >ACMEv1 issuance and renewal brown-outs each month: > >January >* Tuesday, 26th (6 hours) > >February >* Wednesday, 10th - Thursday, 11th (24 hours) >* Thursday, 25th - Friday, 26th (24 hours) > >March >* Monday, 15th - Tuesday, 16th (48 hours) >* Wednesday, 24th - Thursday, 25th (48 hours) > >April >* Tuesday, 6th - Thursday, 8th (72 hours) >* Friday, 23rd - Sunday, 25th (72 hours) > >May >* Thursday, 6th - Monday 10th (5 days) >* Tuesday, 18th - Tuesday, 25th (7 days) > >The Staging ACMEv1 API will be fully disabled on March 26, 2021. Until >that >date, it will undergo brownouts on the same schedule as the Production >ones >above. > >For most people, simply upgrading to the latest version of your >existing >client will suffice to begin using ACMEv2. You can view the client list >at: >https://letsencrypt.org/docs/client-options/ > >If you're unsure how your certificate is managed, get in touch with the > >person who installed the certificate for you. If you don't know who to >contact, please view the help section in our community forum at >https://community.letsencrypt.org/c/help and use the search bar to >check if >there's an existing solution for your question. If there isn't, please >create >a new topic and fill out the help template. > >ACMEv1 API deprecation details can be found in our community forum: >https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1 > >To receive more frequent updates, subscribe to our API Announcements: >https://community.letsencrypt.org/t/about-the-api-announcements-category > > >Thank you for joining us on our mission to create a more secure and >privacy- >respecting Web! > >All the best, > >Let's Encrypt > >If you are receiving this email in error, unsubscribe at: >http://delivery.letsencrypt.org/track/unsub.php?u=30850198&id=68935b8218504d229acda71a697a447e.tw2q0Vc1%2FYCHYi%2Bi%2BbvFqYNb27M%3D&r=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Dr%252A%252A%252A%252A%2540z%252A%252A%252A%252A.%252A%252A%252A >Please note that this would also unsubscribe you from other Let's >Encrypt >service notices, like expiration reminders. >_______________________________________________ >TOPF mailing list -- topf(a)zapf.in >To unsubscribe send an email to topf-leave(a)zapf.in