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.

This bug: 

http://bugs.squid-cache.org/show_bug.cgi?id=3849

was fixed upstream, but doesn't seem to be in the current RHEL7 squid package. 

This means if you use ssl with a cert chain, any clients using newer gnutls will be unable to use your proxy. ;( 

We have hit this with a proxy in Fedora, see: https://fedorahosted.org/fedora-infrastructure/ticket/4682 

Please consider backporting this fix. Thanks.

Created attachment 1011660 [details]
This is a backported patch which should fix bug #1204375

Hi Kevin,

which version of squid and RHEL are you exactly using? I backported this patch, for the latest squid (3.3.8) in RHEL 7.1. I'm attaching the PATCH, so you can try, if it fixes this bug in your squid configuration.

Created attachment 1011700 [details]
SRPM of squid containing patch

We can confirm this fixes the issue. ;) Thanks!

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://rhn.redhat.com/errata/RHSA-2015-2378.html