The packages have been uploaded to Mageia 6 Core Updates Testing. Mageia 6 ships certbot 0.14.2; since then, there have been six releases, each of them containing a lot of bugfixes. This is a therefore a cumulative update. NB: Mageia 6 comes with python-OpenSSL 16.0.0, while newest Certbot requires at least 16.1.0, so python-OpenSSL would need an update, too. This is a minor and 100% backwards compatible update; moreover, the guys from Let's Encrypt were kind enough to perform compatibility tests for python-OpenSSL 16.1.0 + python-cryptography 1.5.3. Suggested advisory: ======================== Certbot 0.20.0 contains multiple bugfixes and improvements. References: https://certbot.eff.org https://github.com/certbot/certbot/blob/master/CHANGELOG.md ======================== Updated packages in core/updates_testing: ======================== python2-acme-0.20.0-1.mga6 python3-acme-0.20.0-1.mga6 python-OpenSSL-16.1.0-1.mga6 python-OpenSSL-doc-16.1.0-1.mga6 python3-OpenSSL-16.1.0-1.mga6 certbot-0.20.0-1.mga6 certbot-doc-0.20.0-1.mga6 certbot-apache-0.20.0-1.mga6 certbot-nginx-0.20.0-1.mga6 Source RPMs: python-acme-0.20.0-1.mga6.src.rpm python-OpenSSL-16.1.0-1.mga6.src.rpm certbot-0.20.0-1.mga6.src.rpm certbot-apache-0.20.0-1.mga6.src.rpm certbot-nginx-0.20.0-1.mga6.src.rpm
Reassigning to QA Team python-acme-0.20.0-1.mga6.src.rpm python-OpenSSL-16.1.0-1.mga6.src.rpm certbot-0.20.0-1.mga6.src.rpm certbot-apache-0.20.0-1.mga6.src.rpm certbot-nginx-0.20.0-1.mga6.src.rpm
Assignee: bugsquad => qa-bugs
I have tested this update as I am willing to use certbot, and it failed for me using apache module with a python OSError in augeas. I have updated all mentioned packages but the error is the same. Here is the error : sudo certbot --apache -d mydomain.com Saving debug log to /var/log/letsencrypt/letsencrypt.log An unexpected error occurred: OSError: library not found: 'augeas' Please see the logfiles in /var/log/letsencrypt for more details. rpm -qa | grep augeas augeas-lenses-1.8.0-1.1.mga6 python3-augeas-1.0.2-3.mga6 lib64augeas0-1.8.0-1.1.mga6
CC: (none) => lists.jjorge
Assignee: qa-bugs => mitya
(In reply to José Jorge from comment #2) > I have tested this update as I am willing to use certbot, and it failed for > me using apache module with a python OSError in augeas. This is a python-augeas bug : it needs libaugeas-devel. Sorry for the noise.
Assignee: mitya => qa-bugsStatus: NEW => ASSIGNED
CC: (none) => mitya
Tested a certificate creation with Let'sEncrypt, all went ok. Pkgs installed : urpmi --searchmedia testing certbot-apache python3-acme python3-OpenSSL
Whiteboard: (none) => MGA6-64-OK
José, thanks for testing! BTW, did you experience the python-augeas bug under Mga6 (stable)? I've failed to reproduce it either on i586 or on x86_64. All the package versions are the same, but libaugeas-devel is not installed, and everything works fine. Here's a short snippet to test it: [user@localhost ~]$ python3 -c "import augeas; a = augeas.Augeas(); print(a)" <augeas.Augeas object at 0x7f56b7f29f98>
Also you might experience another error from Augeas trying to parse erroneous /etc/httpd/conf/conf.d/security.conf (missing closing quotes). That's not a certbot/augeas bug either; should be fixed with our next Apache update.
(In reply to Dimitri Jakov from comment #5) > José, thanks for testing! > > BTW, did you experience the python-augeas bug under Mga6 (stable)? I've > failed to reproduce it either on i586 or on x86_64. All the package versions > are the same, but libaugeas-devel is not installed, and everything works > fine. Here's a short snippet to test it: > > [user@localhost ~]$ python3 -c "import augeas; a = augeas.Augeas(); print(a)" > <augeas.Augeas object at 0x7f56b7f29f98> It's strange, I cannot reproduce this bug anymore now....
MGA6-32 on Dell Latitude D600 MATE No installation issues at first At CLI: # certbot certonly -d <mydummydomain> Saving debug log to /var/log/letsencrypt/letsencrypt.log An unexpected error occurred: OSError: library not found: 'augeas' Please see the logfiles in /var/log/letsencrypt for more details. Installed libaugeas-devel as indicated above, then # certbot certonly -d <mydummydomain> Saving debug log to /var/log/letsencrypt/letsencrypt.log How would you like to authenticate with the ACME CA? ------------------------------------------------------------------------------- 1: Spin up a temporary webserver (standalone) 2: Place files in webroot directory (webroot) ------------------------------------------------------------------------------- Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1 Plugins selected: Authenticator standalone, Installer None Enter email address (used for urgent renewal and security notices) (Enter 'c' to cancel): c An e-mail address or --register-unsafely-without-email must be provided. [root@mach6 ~]# certbot certonly --register-unsafely-without-email -d <mydummydomain> Saving debug log to /var/log/letsencrypt/letsencrypt.log How would you like to authenticate with the ACME CA? ------------------------------------------------------------------------------- 1: Spin up a temporary webserver (standalone) 2: Place files in webroot directory (webroot) ------------------------------------------------------------------------------- Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1 Plugins selected: Authenticator standalone, Installer None Registering without email! ------------------------------------------------------------------------------- Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-v01.api.letsencrypt.org/directory ------------------------------------------------------------------------------- (A)gree/(C)ancel: A Obtaining a new certificate An unexpected error occurred: The request message was malformed :: Error creating new authz :: Name does not end in a public suffix Please see the logfiles in /var/log/letsencrypt for more details. IMPORTANT NOTES: - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. The last response is valid as it is really a dummy domain. Good enough for me.
Whiteboard: MGA6-64-OK => MGA6-64-OK MGA6-32-OKCC: (none) => herman.viaene
Advisory from comment 0. Validating. Thanks to José & Herman for testing this.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2017-0135.html
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED
Tried to install certbot ver 0.20.0-1.mga6.noarch with MCC in mageia 6. MCC gives the following response: Sorry, the following package cannot be selected: - certbot-0.20.0-1.mga6.noarch (due to conflicts with python3-cryptography-2.3.1-1.mga6.x86_64) Seems the issues with certbot are not resolved yet.
CC: (none) => pernel