kvirc / KVIrc

The KVIrc IRC Client
http://www.kvirc.net/
GNU General Public License v2.0
238 stars 75 forks source link

Problem with Rizon BNC server on Ubuntu Lucid #1003

Closed DarthGandalf closed 9 years ago

DarthGandalf commented 9 years ago

Reported by rip on 19 Oct 2010 22:28:13 UTC I have BNC on Rizon server rizonbnc.us.rizon.net and I connect using SSL. I had no problem in kvIRC 4.0.0 RC2 on Ubuntu Lucid. Recently I've upgraded to 4.0.2 and connection suddenly stops.

I mean SSL handshake appears to be ok but then nothing happens. After a while there is an error mesage "Remote end has closed the connection".

I reverted to kvIRC 4.0.0 RC2 and no problem again so this is problem with kvIRC 4.0.2

Note that I tried normal connection (not SSL) and worked OK so it seems like a problem with SSL connections in kvIRC 4.0.2 on Lucid. Don't know if other systems are affected.


Migrated from: https://svn.kvirc.de/kvirc/ticket/1003

DarthGandalf commented 9 years ago

Comment by HelLViS69 on 19 Oct 2010 22:33:56 can you add some info? where did you get the package?

DarthGandalf commented 9 years ago

Comment by ambossarm on 19 Oct 2010 22:44:03 I just tested it and had no problem. but from 4.0.2 to 4.0.0 RC2 is a huge jump and are you sure you are on lucid and that the RC2 package is for lucid and not karmic, because I found no snapshot for lucid with RC2, only some RC3 snapshots?

you may test the latest build from http://www.rzuser.uni-heidelberg.de/~xt1/ubuntu/ did you install the debug package? If yes, does gdb say something about ssl?

DarthGandalf commented 9 years ago

Modified by ctrlaltca on 23 Oct 2010 15:22:16 Resolution: none → need feedback Status: new → closed

DarthGandalf commented 9 years ago

Comment by rip on 25 Oct 2010 15:51:48 It's me again. Sorry for the delay but I had some problems with Net connection. But it's okay now.

@hellvis I got the package from kvirc.net website.

@ambossarm My kvIRC says he's Insomnia 4.0.0 Release Candidate II. I've upgraded from Jaunty to Lucid, maybe that's why. Then again kvIRC should upgade too, right?

I never used Karmic. Skipped it, 'cause I didn't like it. I've upgraded directly to Lucid instead (using Lucid DVD and repo changed to lucid). Ubuntu says to be "Ubuntu 10.04 LTS - Lucid Lynx" (info from Menu=>System=>About Ubuntu) and my GNOME version is 2.30.2 (that's not version from Karmic for sure).

Tried the latest biuld (Equilibrium 4.1.1 - BTW THX ambossarm) but still no luck. Installed kvirc-dbg too, but no complains from gdb. Again SSL handshake seems to be OK, but then nothing happens. And update - I can't connect to BNC without SSL too. But I can connect to normal Rizon IRC server (not BNC). So it's some issue with this particular server.

But still Insomnia 4.0.0 RC2 can connect to Rizon BNC no problem with or without SSL so from my point of view it's still a bug. Though it seems I was wrong, SSL is not an issue here, so I'm changing the name of the topic.

And one more thing, since I have BNC account on Rizon, I cannot use my main nickname on Rizon and cannot identify for it unless I connect using BNC server. So the problem is kinda serious for me...


Resolution: need feedback → none Status: closed → reopened Summary: Connestion using SSL cannot be established on Ubuntu Lucid → Problem with Rizon BNC server on Ubuntu Lucid

DarthGandalf commented 9 years ago

Comment by rip on 25 Oct 2010 16:14:23 Just so you know how it looks like, that's kvirc 4.1.1

Attempting secure connection to rizonbnc.us.rizon.net (Standalone Servers) on port 12345 Looking up the server hostname (rizonbnc.us.rizon.net)... Server hostname resolved to 204.8.34.38 Contacting IRC server rizonbnc.us.rizon.net (204.8.34.38) on port 12345 Low-level transport connection established [rizonbnc.us.rizon.net (204.8.34.38:12345)] Starting Secure Socket Layer handshake [SSL]: Current transmission cipher [SSL]: Cipher: AES256-SHA [SSL]: Version: TLSv1/SSLv3 [SSL]: Bits: 256 (256 used) Secure connection established [rizonbnc.us.rizon.net (204.8.34.38:12345)] Local host address is 78.30.79.154 [SOCKET ERROR]: Remote end has closed the connection Connection terminated [rizonbnc.us.rizon.net (204.8.34.38:12345)]

Same settings, kvirc 4.0.0 RC2

Attempting secure connection to rizonbnc.us.rizon.net (Standalone Servers) on port 12345 Looking up the server hostname (rizonbnc.us.rizon.net)... Server hostname resolved to 204.8.34.38 Contacting IRC server rizonbnc.us.rizon.net (204.8.34.38) on port 12345 Low-level transport connection established [rizonbnc.us.rizon.net (204.8.34.38:12345)] Starting Secure Socket Layer handshake [SSL]: Current transmission cipher [SSL]: Cipher: AES256-SHA [SSL]: Version: TLSv1/SSLv3 [SSL]: Bits: 256 (256 used) Secure connection established [rizonbnc.us.rizon.net (204.8.34.38:12345)] Local host address is 78.30.79.154 Using server specific username (LunarBird) Logging in as LunarBird!LunarBird :rip LunarBird CLH Using server specific password (**) Login operations complete, happy ircing! Welcome to the Rizon Internet Relay Chat Network LunarBird

What's the problem? It's not normal that 4.0.0 RC2 version can do something 4.1.1 cannot, right?

DarthGandalf commented 9 years ago

Comment by ctrlaltca on 25 Oct 2010 16:19:37 duplicate of #719, #787. Please take a look at the https://svn.kvirc.de/kvirc/wiki/FAQ , number 5


Resolution: none → duplicate Status: reopened → closed

DarthGandalf commented 9 years ago

Comment by rip on 25 Oct 2010 17:41:10 The oldest "bug" known - not reading FAQ by the user, lol. Guess I've made a fool of myself. Then again it wouldn't hurt if kvirc could autodetect the problem and displayed a message: "If it's a bouncer you're trying to connect, then turn off CAP protocol in server settings, you dolt!" or STH like that ;)

DarthGandalf commented 9 years ago

Comment by rip on 25 Oct 2010 17:52:48 BTW - There's an error in your FAQ. The FAQ says to disable an option "Use CAP protocol" on second tab "Connection". That's wrong, there's no such option. It's on the last tab "Advanced" and the name of the option is "Query advanced capabilities on connect".

DarthGandalf commented 9 years ago

Comment by ctrlaltca on 26 Oct 2010 06:59:16 Thank you.. as you can see, the oldest problem for developers is to keep documentation updated :)