Bug 24004

Summary:	certbot crashes missing pyasn1
Product:	Mageia	Reporter:	José Jorge <lists.jjorge>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	herman.viaene, lewyssmith, mageia, smelror, sysadmin-bugs
Version:	6	Keywords:	advisory, validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA6-32-OK MGA6-64-OK
Source RPM:	certbot	CVE:
Status comment:

Description José Jorge 2018-12-14 13:48:12 CET

While it worked, certbot stopped working after cleaning orphans in a MGA6 server.

The problem is that package python3-pyasn1 was missing :

systemd[1]: certbot-renew.service: Main process exited, code=exited, status=1/FAILURE
déc. 14 08:04:26 xx certbot[3433]: pkg_resources.DistributionNotFound: The 'pyasn1' distribution was not found and 
déc. 14 08:04:26 xx certbot[3433]:     raise DistributionNotFound(req, requirers)
déc. 14 08:04:26 xx certbot[3433]:   File "/usr/lib/python3.5/site-packages/pkg_resources/__init__.py", line 828, i
déc. 14 08:04:26 xx certbot[3433]:     needed = self.resolve(parse_requirements(requirements))

Comment 1 Stig-Ørjan Smelror 2018-12-14 13:58:43 CET

Advisory
========

certbot has been updated with missing python3-pyasn1.


Files
=====

Uploaded to core/updates_testing

certbot-0.20.0-3.mga6
certbot-doc-0.20.0-3.mga6

from certbot-0.20.0-3.mga6.src.rpm

CC: (none) => smelror

Comment 2 Herman Viaene 2018-12-15 10:58:31 CET

MGA6-32 MATE on IBM Thinkpad R50e
Confirm that python3-pyasn1 is drawn in as dependency at installation.
At CLI:
$ certbot -h

-------------------------------------------------------------------------------

  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate. The most common SUBCOMMANDS and flags are:
etc......
At least it does not crash.
# certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log

-------------------------------------------------------------------------------
No certs found.
-------------------------------------------------------------------------------

# certbot certonly --test-cert
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): c
Could not choose appropriate plugin: authenticator could not be determined or is not installed
authenticator could not be determined or is not installed

I am not familiar at all with this stuff, so not venturing any further.At least the working without errors or crashes has been demonstrated
For more info if someone likes to venture further, see https://certbot.eff.org/docs/using.html

CC: (none) => herman.viaene
Whiteboard: (none) => MGA6-32-OK

Comment 3 PC LX 2018-12-15 13:17:35 CET

Installed and tested without issues.

Tests included:
- creating a certificate/key pair for a domain, using webroot authentication;
- listing certificates;
- periodic certificates renewing (no certificates due for renewal at this moment).

System: Mageia 6, x86_64, Intel CPU.

$ uname -a
Linux marte 4.14.78-desktop-1.mga6 #1 SMP Sun Oct 21 20:31:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q certbot
certbot-0.20.0-3.mga6

Whiteboard: MGA6-32-OK => MGA6-32-OK MGA6-64-OK
CC: (none) => mageia

Comment 4 Lewis Smith 2018-12-15 21:02:40 CET

Thank you Herman & PC_LX. Validating; advisory from comment 1.

Keywords: (none) => advisory, validated_update
CC: (none) => lewyssmith, sysadmin-bugs

Comment 5 Mageia Robot 2018-12-15 22:30:44 CET

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0183.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED