Projet

Général

Profil

Demande #4301

ACTION REQUIRED: Renew these Let's Encrypt certificates by March 4

Ajouté par Christian P. Momon il y a environ 4 ans. Mis à jour il y a environ 4 ans.

Statut:
Fermé
Priorité:
Normale
Assigné à:
Catégorie:
-
Version cible:
Début:
04/03/2020
Echéance:
% réalisé:

0%

Temps estimé:
Difficulté:
2 Facile

Description

L'information a été diffusée :
https://www.nextinpact.com/brief/let-s-encrypt---trois-millions-de-certificats-revoques-a-cause-d-un-bug-11487.htm
https://community.letsencrypt.org/t/revoking-certain-certificates-on-march-4/114864
https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591

Le 03/03/2020 à 11:27, a écrit :

Sujet : ACTION REQUIRED: Renew these Let's Encrypt certificates by March 4
Date : Tue, 03 Mar 2020 10:27:54 +0000

We recently discovered a bug in the Let's Encrypt certificate authority code, 
described here:

https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591

Unfortunately, this means we need to revoke the certificates that were affected 
by this bug, which includes one or more of your certificates. To avoid 
disruption, you'll need to renew and replace your affected certificate(s) by 
Wednesday, March 4, 2020. We sincerely apologize for the issue.

If you're not able to renew your certificate by March 4, the date we are 
required to revoke these certificates, visitors to your site will see security 
warnings until you do renew the certificate. Your ACME client documentation 
should explain how to renew.

If you are using Certbot, the command to renew is:

certbot renew --force-renewal

If you need help, please visit our community support forum: 
https://community.letsencrypt.org/t/revoking-certain-certificates-on-march-4/114864

Please search thoroughly for a solution before you post a new question. Let's 
Encrypt staff will help our community try to answer unresolved questions as 
quickly as possible.

Your affected certificate(s), listed by serial number and domain names:

04092a89c01d6f06818970ddee2a7a4b89d5: 2007.libre-en-fete.net 2007.libre-en-fete.org 2008.libre-en-fete.net 2008.libre-en-fete.org 2009.libre-en-fete.net 2009.libre-en-fete.org 2010.libre-en-fete.net 2010.libre-en-fete.org 2011.libre-en-fete.net 2011.libre-en-fete.org 2012.libre-en-fete.net 2012.libre-en-fete.org 2013.libre-en-fete.net 2013.libre-en-fete.org 2014.libre-en-fete.net 2014.libre-en-fete.org 2015.libre-en-fete.net 2015.libre-en-fete.org 2016.libre-en-fete.net 2016.libre-en-fete.org 2017.libre-en-fete.net 2017.libre-en-fete.org 2018.libre-en-fete.net 2018.libre-en-fete.org 2019.libre-en-fete.net 2019.libre-en-fete.org libre-en-fete.net libre-en-fete.org spip.libre-en-fete.net spip.libre-en-fete.org www.libre-en-fete.net www.libre-en-fete.org
03fd87e1c54bf66dcb163274889b3ff994fe: *.april.org april.org

If you are receiving this email in error, unsubscribe at:
  http://mandrillapp.com/track/unsub.php?u=30850198&id=9ed3a4f20f1f435a88f095306bc09dfb.OZVTgP3hMZewU2Xohifn6oGfvL8%3D&r=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Dadmins-auto%2540april.org
Please note that this would also unsubscribe you from other Let's Encrypt 
service notices, like expiration reminders.

Demande : renouveler manuellement les certificats nécessaires.

Historique

#1

Mis à jour par Christian P. Momon il y a environ 4 ans

  • Description mis à jour (diff)
#2

Mis à jour par Christian P. Momon il y a environ 4 ans

  • Statut changé de Nouveau à Résolu
  • Assigné à mis à Quentin Gibeaux

Actions par QGuLL :

résolu :
certbot renew --force-renewal --webroot -w /var/www/acme-challenge --cert-name libre-en-fete.net
certbot renew --force-renewal --cert-name april.org --preferred-challenges=dns --manual-auth-hook /srv/scripts/bastion/update-dns-acme-challenge.sh
/etc/letsencrypt/letsencrypt_post-hook.sh

Vérifié via Firefox, la date du certificat est bien celle de maintenant.

#3

Mis à jour par Quentin Gibeaux il y a environ 4 ans

  • Statut changé de Résolu à Fermé

Formats disponibles : Atom PDF