xchat2 needs upgrading

[wagle@…]

openssl and xchat2 need upgrading, current xchat2 can't talk to ssl irc servers:

* Connection failed. Error: (336151568) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

According to this url:

 http://bugs.archlinux.org/task/13882

later versions of openssl and xchat2 work

[wagle@…]

Cc Me!

[jmr@…]

Openssl 0.9.8k is already the latest version.

[wagle@…]

if you built xchat2 +ssl in a brand new /opt/local early this week (takes me several hours), then the xchat will not be able to talk to ssl irc servers. before giving up and reverting to my 9 month old /opt/local, I did an install of openssl 0.9.8i, and xchat worked (but it was a crazy version involving +quartz and +no_x11, so I threw it out by reverting).

I don't know what the deal is with various versions of openssl. Rebuilding macports takes me several days of downtime, so isn't something I can do a lot.

Is it me that needs to fool with figuring out what's going on with openssl?

[afb@…]

MacPorts xchat2 @2.8.6_2 is the same version (and patches) as ArchLinux xchat 2.8.6-3

[wagle@…]

actually xchat2 with ssl does not work. marking it invalid without testing is very impressive.

[blb@…]

Connecting to the OFTC server with SSL works fine for me, which server is failing?

$ port installed xchat2 openssl
The following ports are currently installed:
  openssl @0.9.8k_0 (active)
  xchat2 @2.8.6_2+ssl (active)

I do note, however, that the +ssl should add a dependency to the openssl port...

[afb@…]

Replying to wagle@…:

marking it invalid without testing is very impressive.

But apparently upgrading openssl/xchat is not it either...

[wagle@…]

Ok, I will rebuild and test various servers, and find one I am permitted to tell you about so you can repeat it.

[wagle@…]

Replying to wagle@…:

Ok, I will rebuild and test various servers, and find one I am permitted to tell you about so you can repeat it.

Turned out I (mysteriously) had a list of two irc servers in my xchat config. With the older openssl, this wasn't noticed. With the new openssl, it was, and it failed.