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.
DescriptionAnn Marie Rubin
2015-05-13 15:00:57 UTC
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
<t8m> it could be the same problem or not, this just signalls that the ssl server does not like the client
<arubin> how do I find out what it doesn't like and what I need to change?
<t8m> could you give me the address of the server?
<arubin> irc.linux.hp.com
<arubin> port = "994"
<arubin> I wonder if it has to do with poodle
<arubin> https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1381484
<t8m> hmm I am able to connect with Fedora
<t8m> Fedora 21
<t8m> it is possible that the RHEL 7 CSB xchat is broken
<arubin> can you connect to the hp irc channel
<t8m> that it uses SSL3 only
<arubin> it was also broken on RHEL 6
<arubin> that's why I upgraded to RHEL 7
<t8m> I can connect there fine
<arubin> I wonder if HP server disabled sslv3 because of poodle and xchat only uses sslv3 to connect
<t8m> yes
<t8m> that's most probable
<arubin> are you connecting with sslv3?
<t8m> Probably not
<t8m> I would have to look at the network packets
<arubin> can I change the way I connect to use TLS?
<arubin> configure it?
<t8m> I am afraid it is hardcoded
tried disabling ssl in the xchat client connection:
Cycling to next server in ChatNet...
* Disconnected ().
* Looking up irc.linux.hp.com
* Connecting to people.linux.hp.com (15.250.148.100) port 994...
* Connected. Now logging in...
* Disconnected (Connection reset by peer).
There is no way to change xchat to use TLS