Bug 96661 - kopete irc plugin crash ssl
Summary: kopete irc plugin crash ssl
Status: RESOLVED DUPLICATE of bug 90212
Alias: None
Product: kopete
Classification: Unmaintained
Component: IRC Plugin (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-09 21:10 UTC by djandruczyk
Modified: 2005-01-20 02:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
ksslsocket.diff (1.36 KB, text/x-diff)
2005-01-12 20:22 UTC, Michel Hermier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description djandruczyk 2005-01-09 21:10:24 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux

If "Prefer SSL based connections" is set when setting up an IRC account Kopete will crash when attampting to connect to and IRC network (efnet was my choice)

Messages trapped from the console using "kopete --nofork"

 kopete --nofork
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QObject::connect: No such slot IRCContactManager::slotNewAction(const QString&,c
onst QString&,const QString&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such slot IRCContactManager::slotNewPrivAction(const QStrin
g&,const QString&,const QString&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
kopete: WARNING: [static QString KopeteMessage::decodeString(const QCString&, co
nst QTextCodec*, bool*)] Unable to decode string using provided codec(s), taking
 best guesses!
kopete: WARNING: [static QString KopeteMessage::decodeString(const QCString&, co
nst QTextCodec*, bool*)] Unable to decode string using provided codec(s), taking
 best guesses!
kopete: WARNING: [static QString KopeteMessage::decodeString(const QCString&, co
nst QTextCodec*, bool*)] Unable to decode string using provided codec(s), taking
 best guesses!
QGArray::find: Index 0 out of range
kdecore (KSocket): ERROR: KExtendedSocket::connectionEvent() called but no data 
available!
QGArray::find: Index 0 out of range
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined 
symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined 
symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined 
symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined 
symbol: OpenSSL_add_all_algorithms_noconf
32658:error:140770FC:lib(20):func(119):reason(252):s23_clnt.c:475:
KCrash: Application 'kopete' crashing...


A strings test on /usr/lib/libcrypto.so.0.9.7 shows those functions missing,  but a couple were spelled differently:
OPENSSL_add_all_algorithms_conf  (instead of OpenSSL...)
OPENSSL_add_all_algorithms_noconf (instead of (OpenSSL...)
PKCS7_ENC_CONTENT_free  (not sure if this is related to PKCS7_content_free)

/usr/lib/libcrypto-so.0.9.7 is from 
dev-libs/openssl-0.9.7d-r2
Comment 1 Michel Hermier 2005-01-10 20:14:12 UTC
kssl using openssl problem. Check the openssl version that you should use for 
your kdelibs installation.
This bug is a duplicate (don't had investigated for the number).

Comment 2 djandruczyk 2005-01-12 16:08:44 UTC
I checked's my local "use" flags for gentoo,  ssl wasn't in my flags but it was in the global flags.  I added it anyway and recompiled all apps that depended on it and kopete still crashes withthe same basic error..

What OpenSSL version does KDE-3.3.2 REQUIRE?  it's possible the gentoo openssl is out of date, and the gentoo KDE ebuild maintainers don't know it...

Comment 3 Michel Hermier 2005-01-12 20:22:51 UTC
I don't found any reference about the SSL version to use :(.

Let's try another way! Another assumption is that the connection code fail for 
some reasons, and so we try to use some not initialized data, which is also 
related with other SSL bugs.
Can you try the following patch for this? I'm currently unable to test due to 
cvs HEAD problem (wild guess Jason?), but it compiles.


Created an attachment (id=9058)
ksslsocket.diff
Comment 4 Jason Keirstead 2005-01-20 02:10:29 UTC
Marking as dup of 90212, it has more votes

*** This bug has been marked as a duplicate of 90212 ***