Bug 24380 - Letsencrypt changes the authentication method
Summary: Letsencrypt changes the authentication method
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Dimitri Jakov
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-18 07:46 CET by Muhammad Tailounie
Modified: 2020-08-16 22:34 CEST (History)
3 users (show)

See Also:
Source RPM: Certbot
CVE:
Status comment:


Attachments

Description Muhammad Tailounie 2019-02-18 07:46:43 CET
Certbot client is no more capable of renewing Letsencrypt certificates due to changes in the authentication method.

Letsencrypt recommends certbot client version to be 0.28 and higher.

Any system running Mageia, using Letsencrypt certificates and relying on certbot client to renew those certificate is having a problem now.
Comment 1 Johnny A. Solbu 2019-02-18 10:50:03 CET
I agree that it shoudl be updated.

But untill the certbot is updated, there is a way around it.
We still run certbot 0.10 on a Debian server, and this server is still able to renew and get new certificates.

One just have to change the authenticator from apache to webroot.
So we use webroot for authentication and use apache as the installer. 

The command we use is: 
certbot --test-cert --authenticator webroot --installer apache -d example.net -d www.example.net --webroot -w /var/www/html

CC: (none) => cooker

Comment 2 Marja Van Waes 2019-02-19 08:57:38 CET
Assigning to the registered maintainer.

CC: (none) => marja11
Assignee: bugsquad => mitya

Comment 3 Aurelien Oudelet 2020-08-16 22:34:09 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

CC: (none) => ouaurelien
Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.