konversation locked in a "checking crypto certificate" cycle

[Steve McInerney]

Binary package hint: konversation

Trying to access a self-signed certificate'ed SSL IRC server.
After happily accessing same server ever since Intrepid upgrade, this time konversation came up with a "self signed certificate" warning.

I (mistakenly) chose to verify the certificate and got "stuck". Wouldn't budge off the displayed certificate window. No matter which buttons or even 'close window' chosen, it's flash and stay there.

Only solution to regain "control" of konversation was kill or xkill.

The *workaround* to regain proper access was to manually edite ~/.kde/share/config/konversationrc and set:
SslIpCNMismatch=yes
to
SslIpCNMismatch=no

for the server section in question.

Without doing an exhaustive search of backups, the change appears to have been related to the removal of:
SslCertificateNotAuthentic=no
from the same location,
AND the changing of SslIpCNMismatch=no (which is what was in there some days ago) to yes.

[Steve McInerney (spm)]

I should point out - by regain control - I mean that killing and restarting would immediately drop back at the same "stuck" place.
ie Start konversation, it'd get stuck; do a complete: kill/reboot, start again; and wind up at the same stuck place.