Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
SSL using client certificate works with curl but not with ostree.
CURL:
curl -v -k --cert ./ostree-crt-key.pem
<HOST>/pulp/ostree/web/Default_Organization/Dev/atomic_cv/content/dist/rhel/atomic/7/7Server/x86_64/ostree/repo/summary
OSTREE:
[root@qe-capsule-upgrade-rhel7 ostree]# cat config
[core]
repo_version=1
mode=archive-z2
[remote "satellite"]
url=<HOST>/pulp/ostree/web/Default_Organization/Dev/atomic_cv/content/dist/rhel/atomic/7/7Server/x86_64/ostree/repo
tls-permissive=true
tls-client-cert-path=/root/ostree-crt-key.pem
tls-client-key-path=/root/ostree-crt-key.pem
[root@qe-capsule-upgrade-rhel7 ostree]# ostree remote refs --repo=.
satellite
error: Error performing TLS handshake: A TLS fatal alert has been
received.
On Satellite: AH02261: Re-negotiation handshake failed: Not accepted by
client!?
Both <HOST> and certificates supplied in private comment.
Version-Release number of selected component (if applicable):
ostree-2017.1-2.atomic.el7.x86_64
libsoup-2.48.1-6.el7.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Create repository.
2. Create remote using attached certificate.
3.
Actual results:
AH02261: Re-negotiation handshake failed
Expected results:
No error.
Additional info:
There are libsoup/glib-networking bugs in this area; see e.g. https://bugzilla.gnome.org/show_bug.cgi?id=781578
In Fedora 26+, we have switched ostree to libcurl (matching NetworkManager), and libcurl in Fedora uses OpenSSL. It's possible this will be backported to RHEL at some point.
We just confirmed actually that `--with-curl` to ostree-2017.7-2 in RHEL works.
Doesn't tell us whether or not the bug is in ostree's libsoup code, libsoup/glib-networking, or gnutls, but I suspect libsoup/glib-networking.
Comment 11Nikos Mavrogiannopoulos
2017-07-14 05:53:50 UTC
I'm not sure if the two issues are related but I'd move the bug there to be addressed. Even if ostree moves its back-end, the issue would remain.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2952