Bug 129963

Summary:	connecting via ssl can result in a failed connect if the security dialog is not dealt with soon enough
Product:	[Applications] konversation	Reporter:	Dan Meltzer <hydrogen>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	hein, johnjaylward, Marcus
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	1.5
Sentry Crash Report:

Description Dan Meltzer 2006-06-28 14:27:58 UTC

Version:           0.19+ #3109 (using KDE 3.5.3, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.16-ck10-20060514

With auto-reconnect (or just plain going afk when turning the computer on) and connecting to a ssl server, if the dialog about accepting the cert is up for more than three minutes, the connection to the server times out.  After hitting accept it does not try and reconnect, it just gets stuck at connecting to server.  The only way to fix this is to close the tab and reopen it.

Comment 1 Marcus Wolschon 2006-12-20 23:44:41 UTC

I am constantly annoyed by this bug too.

Comment 2 John Aylward 2008-08-20 23:25:09 UTC

it would be nice if there was an option to accept all certifics even if invalid, but only on a per-network option. Some networks use properly signed certs, so it'd be bad if the option was enable and a bad cert was there.

Comment 3 Myriam Schweingruber 2013-04-14 09:14:55 UTC

Is this still valid for Konversation 1.4 or 1.5 RC1?

Comment 4 Eike Hein 2013-04-14 17:34:35 UTC

I believe I fixed this in the last rework of the logic dealing with the dialog. The connection can still timeout while the dialog is up of course, but it should recover more gracefully now.