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:
Cannot connect to any FreeNode IRC servers using SASL (which now appears to be required on many, if not all, servers). This is because the pidgin client cannot handle the "EXTERNAL" authentication method advertised by the server.

FreeNode is the largest and most popular IRC server network, and being unable to connect to it at all in EL7 is unacceptable.

Version-Release number of selected component (if applicable):
pidgin-2.10.7-26.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Connect to chat.freenode.net on port 7000 with over SSL with SASL authentication

Actual results:
Fails to connect.

Expected results:
Should connect.

Additional info:
This bug was reported against Debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847674 and upstream at https://pidgin.im/pipermail/support/2016-September/029627.html and fixed in upstream with https://bitbucket.org/pidgin/main/commits/610656636af6d1d6fdd6723d5ef311c903b6a804?at=default

I applied the upstream patch to the source RPM I got from CentOS 7 and rebuilt from source. I then installed the updated version of pidgin and libpurple to test, and can confirm that it fixes this bug.

Created attachment 1269909 [details]
upstream-sasl-fix

Uploaded upstream patch from https://bitbucket.org/pidgin/main/commits/610656636af6d1d6fdd6723d5ef311c903b6a804/raw

Still broken in 7.4 with pidgin-2.10.11-5.el7
This is a trivial patch to apply, which is fixed in upstream as of 2.12.0
Please fix.

Here's a scratch build:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20652569

Built pidgin-2.10.11-8.el7:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20662915

This ought to be part of https://errata.devel.redhat.com/advisory/38320 instead.

Works with version pidgin-2.10.11-8.el7.x86_64.

I'm able to connect to chat.freenode.net:7000 with SSL and SASL authentication. Sanity tests passed as well.

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-2019:2044