Bug 1750121 - Unable to "Open URL" with https.
Summary: Unable to "Open URL" with https.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timotheus Pokorra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-08 15:01 UTC by Dr. Tilmann Bubeck
Modified: 2019-11-27 00:23 UTC (History)
9 users (show)

Fixed In Version: mono-5.20.1-2.fc31
Clone Of:
Environment:
Last Closed: 2019-11-27 00:23:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dr. Tilmann Bubeck 2019-09-08 15:01:19 UTC 
Description of problem:

Using "Open URL" with a https URL leads to error message:
"TrustFailure (Authentication failed, see inner exception.)"

Everything works fine with a http URL.

Version-Release number of selected component (if applicable):
keepass-2.41-3.fc30.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start keepass
2. Use "File>Open>Open URL"
3. Enter URL "https://www.bubecks.de/dav/bubeck/zugaenge-tbubeck.kdbx"

Actual results:
"TrustFailure (Authentication failed, see inner exception.)"

Expected results:
"(401) Unauthorized"
Because no user/pw is given. If you would enter a valud user/pw it succeeds

Additional info:
http works, https does not.
Using the keepass from https://keepass.info/download.html works also with https
Comment 1 Peter Oliver 2019-09-22 11:48:26 UTC 
Does running `sudo cert-sync /etc/pki/tls/certs/ca-bundle.crt` solve this for you?
Comment 2 Dr. Tilmann Bubeck 2019-09-22 12:29:13 UTC 
YES, it does.

(I tried it once more before cert-sync, to make sure, that it still not worked. It failed. After "cert-sync" it works without problems).
Comment 3 Peter Oliver 2019-10-13 17:01:43 UTC 
Raised pull request https://src.fedoraproject.org/rpms/mono/pull-request/3.
Comment 4 Dr. Tilmann Bubeck 2019-11-17 13:35:12 UTC 
cert-sync still needed in fc31 with keepass-2.42.1-3.fc31.x86_64
After cert-sync everything works.
Comment 5 Dr. Tilmann Bubeck 2019-11-17 13:42:25 UTC 
FC31 still uses mono-core-5.20.1-1.fc31.x86_64 and I see you PR went into 5.20.1-2 at https://koji.fedoraproject.org/koji/buildinfo?buildID=1399968
Is there a Bodhi Update request for 5.20.1-2 missing?
Comment 6 Fedora Update System 2019-11-17 20:22:54 UTC 
FEDORA-2019-9ef37b01aa has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9ef37b01aa
Comment 7 Timotheus Pokorra 2019-11-17 20:24:32 UTC 
Thanks for the reminder. I must have forgotten about it, after initiating the build. Now the bodhi update is on its way.
Comment 8 Fedora Update System 2019-11-18 02:15:08 UTC 
mono-5.20.1-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9ef37b01aa
Comment 9 Fedora Update System 2019-11-27 00:23:25 UTC 
mono-5.20.1-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.