Bug 1592178 - CERTIFICATE_VERIFY_FAILED
Summary: CERTIFICATE_VERIFY_FAILED
Keywords:
Status: CLOSED DUPLICATE of bug 1591094
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 04:04 UTC by Lance Haverkamp
Modified: 2018-09-21 06:54 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-09-21 06:54:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lance Haverkamp 2018-06-18 04:04:13 UTC
This is a repost, as the last report mysteriously vanished: 

trusted root certificates apparently missing from mono, and do not properly install using Mono's suggested command:

I'm trying to run the Duplicati backup program, which relies on mono. Getting CERTIFICATE_VERIFY_FAILED error.

The mono documentation indicates that RedHat/Fedora/Centos should already have the trusted root certificates in Mono, but if not, they can be added with the following command:

sudo cert-sync /etc/pki/tls/certs/ca-bundle.crt

But that's returning:

Unhandled Exception:
System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x0002b] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00065] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.TermInfoDriver..ctor (System.String term) [0x00058] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.ConsoleDriver..cctor () [0x00062] in <373b6e083d6e45e498c9082a8eebd27f>:0
--- End of inner exception stack trace ---
at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x0000a] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Console..cctor () [0x000a8] in <373b6e083d6e45e498c9082a8eebd27f>:0
--- End of inner exception stack trace ---
at Mono.Tools.CertSync.Main (System.String[] args) [0x00037] in <e14d5123bc22484f8e0510200156fa93>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x0002b] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00065] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.TermInfoDriver..ctor (System.String term) [0x00058] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.ConsoleDriver..cctor () [0x00062] in <373b6e083d6e45e498c9082a8eebd27f>:0
--- End of inner exception stack trace ---
at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x0000a] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Console..cctor () [0x000a8] in <373b6e083d6e45e498c9082a8eebd27f>:0
--- End of inner exception stack trace ---
at Mono.Tools.CertSync.Main (System.String[] args) [0x00037] in <e14d5123bc22484f8e0510200156fa93>:0

Comment 1 Timotheus Pokorra 2018-06-19 05:59:39 UTC
I marked your bug 1591094 as duplicate of bug 1580447 because I think it is the same, meaning it has the same root of the problem, and should be fixed in Fedora 28 updates.

Comment 2 Timotheus Pokorra 2018-09-21 06:54:46 UTC

*** This bug has been marked as a duplicate of bug 1591094 ***


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