Bug 47375 - diagnostic test for SSL certificates fails with Lets Encrypt certs (signed_chain.crt: verification failed)
diagnostic test for SSL certificates fails with Lets Encrypt certs (signed_ch...
Status: RESOLVED WORKSFORME
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
UCS 4.3
Other All
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-18 16:31 CEST by Dirk Ahrnke
Modified: 2018-07-19 16:22 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Ahrnke 2018-07-18 16:31:24 CEST
as reported in https://help.univention.com/t/problems-in-systemdiagnose/7106/10 there is a new error in system diagnostics when using Lets Encrypt:


Found invalid certificate '/etc/univention/letsencrypt/signed_chain.crt': error /etc/univention/letsencrypt/signed_chain.crt: verification failed

verified using UCS 4.3-1 errata151 + Lets Encrypt 	1.2.2-3

Note: the error message is different to #45702
Comment 1 Valentin Heidelberger univentionstaff 2018-07-19 11:24:44 CEST
The error happens, because the Let's Encrypt CA isn't in the global CA store of UCS by default.
The app adds it's CA to the store, but it has to be updated manually afterwards using the following command:

update-ca-certificates

The app used to do this by itself, but it turned out that that doesn't succeed reliably with the App Center open (which is usually the case when installing and configuring the app).

Therefore the app's README, which is shown on the app page after the installation, gives a hint to this command.

It's planned to modify the app in such a way that modifying the CA store isn't necessary anymore.
Comment 2 Dirk Ahrnke 2018-07-19 11:35:46 CEST
Ok, if there would be a status "WORKSFORME" in this bugtracker I would choose it now. I am unsure if "RESOLVED" is the way to go.

However I would suggest to enhance the README app in a way that it is more clear that omitting the "update-ca-certificates" would cause the error message. I guess that the relation between curl and system diags is not evident for most users.
Comment 3 Dirk Ahrnke 2018-07-19 16:22:03 CEST
(In reply to Dirk Ahrnke from comment #2)
> Ok, if there would be a status "WORKSFORME" in this bugtracker I would
> choose it now. I am unsure if "RESOLVED" is the way to go.

nevermind