Hello kopete users,
if you are using the cryptoplugin of kopete you might be also annoyed by the visual overhead ("Outgoing Encrypted Message:") which is constantly printed with each incoming and outgoing message and consumes more space than the real messages. Long ago there has been a bug report on this issue (https://bugs.kde.org/show_bug.cgi?id=77486), a patch was submitted and the bug was closed as fixed, but the patch never came into a final Debian or Ubuntu release, I think because of KDE4. But what about applying this patch against the KDE3 remix repository now?
The patch is hosted here: http://kde-apps.org/content/show.php?content=40844&vote=good&tan=751...
I also would like to help getting this patch applied. But I had some problem with the compilation of the kopete package. Normally I just do
apt-get build-dep <package> apt-get -b source <package>
and the binary package is generated from the source package. But in case of kopete-kde3 the compilation fails with this error:
[...] g++ -DHAVE_CONFIG_H -I. -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise -I../../../.. -I../../../../kopete/protocols/gadu/libgadu -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise/qca/src -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise -I/opt/kde3/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_LARGE_FILES=1 -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c /home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise/rtf.cc -fPIC -DPIC -o .libs/rtf.o rtf.ll: In member function 'void RTF2HTML::PrintUnquoted(const char*, ...)': rtf.ll:316: warning: function might be possible candidate for 'gnu_printf' format attribute rtf.ll: In member function 'void Level::setText(const char*)': rtf.ll:574: error: invalid conversion from 'const char*' to 'char*' make[7]: *** [rtf.lo] Error 1 make[7]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise/libgroupwise' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise/libgroupwise' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2
I'm using karmic with some lucid packages (libc6). Is this the reason for the error? Does somebody know who to fix it?
Thanks in advance.
Regards, Stefan
On Sun, November 15, 2009 5:10 am, Stefan Endrullis wrote:
Hello kopete users,
if you are using the cryptoplugin of kopete you might be also annoyed by the visual overhead ("Outgoing Encrypted Message:") which is constantly printed with each incoming and outgoing message and consumes more space than the real messages. Long ago there has been a bug report on this issue (https://bugs.kde.org/show_bug.cgi?id=77486), a patch was submitted and the bug was closed as fixed, but the patch never came into a final Debian or Ubuntu release, I think because of KDE4. But what about applying this patch against the KDE3 remix repository now?
The patch is hosted here: http://kde-apps.org/content/show.php?content=40844&vote=good&tan=751...
I also would like to help getting this patch applied. But I had some problem with the compilation of the kopete package. Normally I just do
apt-get build-dep <package> apt-get -b source <package>
and the binary package is generated from the source package. But in case of kopete-kde3 the compilation fails with this error:
[...] g++ -DHAVE_CONFIG_H -I. -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise -I../../../.. -I../../../../kopete/protocols/gadu/libgadu -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise/qca/src -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise -I/opt/kde3/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_LARGE_FILES=1 -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c /home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise/rtf.cc -fPIC -DPIC -o .libs/rtf.o rtf.ll: In member function 'void RTF2HTML::PrintUnquoted(const char*, ...)': rtf.ll:316: warning: function might be possible candidate for 'gnu_printf' format attribute rtf.ll: In member function 'void Level::setText(const char*)': rtf.ll:574: error: invalid conversion from 'const char*' to 'char*' make[7]: *** [rtf.lo] Error 1 make[7]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise/libgroupwise' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise/libgroupwise' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2
I'm using karmic with some lucid packages (libc6). Is this the reason for the error? Does somebody know who to fix it?
Thanks in advance.
Regards, Stefan
Hi Stefan,
GCC 4.4 changed char * strchr ( const char * str, int character ); to const char * strchr ( const char * str, int character );
This forces every instance of char xyz = strchr(...) to be changed to the (more correct) const char xyz = strchr(...). Fixing this is a simple matter of hunting down the offending line and adding a const keyword to the variable (unless, of course, the programmer was doing Bad Things with the variable, but fortunately I haven't seen too much of that in KDE3).
Hope this helps, and thanks for the assistance!
Timothy Pearson KDE3.5 Maintainer/Developer
Just since the topic came up: I use the OTR plugin and found that to be rather good, it's cross platform, available for kopete, pidgin, trillian pro and others.
Your right, OTR has some advantages over the GPG plugin, but it has also a major disadvantage. You cannot send encrypted offline messages. At least not with the OTR plugin of kopete 0.12. Therefore I still prefer the normal crypto plugin.
Regards, Stefan
Dexter Filmore wrote:
Just since the topic came up: I use the OTR plugin and found that to be rather good, it's cross platform, available for kopete, pidgin, trillian pro and others.
Yes, I notced that, too and it's a bit annoying, given. But otherwise it works so well and is so easy to setup that I still recommend it. Any idea why it can't store offline messages?
Am Sonntag, 15. November 2009 23:27:19 schrieb Stefan Endrullis:
Your right, OTR has some advantages over the GPG plugin, but it has also a major disadvantage. You cannot send encrypted offline messages. At least not with the OTR plugin of kopete 0.12. Therefore I still prefer the normal crypto plugin.
Regards, Stefan
Dexter Filmore wrote:
Just since the topic came up: I use the OTR plugin and found that to be rather good, it's cross platform, available for kopete, pidgin, trillian pro and others.
I think it's because OTR negotiates the encryption key for each chat session. This is part of the OTR idea/protocol. If you go offline with your OTR client the session key gets invalid, because the other side cannot know which client you're going to use next. If it's the same client as before I would be theoretically able to decrypt the offline messages, since this client could know the last negotiated session key. But if you use another IM client (maybe on another computer) you're not able to decrypt the offline messages as long as you don't transfer the last session key to this client. BTW, I think the clients deletes the session keys after a session for security reasons. Some OTR compatible IM clients are even so dump that they think the chat session gets closed when the user closes the chat window. With those clients it's even hard to get an encrypted session working when both users are online. In the beginning I was very excited by OTR, but after some weeks of fighting w ith those teething problems I finally deactivated it and went back to the old crypto plugin. But maybe you don't have those problems with other clients. As long as you are satisfied with OTR you should not change it.
Regards, Stefan
Dexter Filmore schrieb:
Yes, I notced that, too and it's a bit annoying, given. But otherwise it works so well and is so easy to setup that I still recommend it. Any idea why it can't store offline messages?
Am Sonntag, 15. November 2009 23:27:19 schrieb Stefan Endrullis:
Your right, OTR has some advantages over the GPG plugin, but it has also a major disadvantage. You cannot send encrypted offline messages. At least not with the OTR plugin of kopete 0.12. Therefore I still prefer the normal crypto plugin.
Regards, Stefan
Dexter Filmore wrote:
Just since the topic came up: I use the OTR plugin and found that to be rather good, it's cross platform, available for kopete, pidgin, trillian pro and others.
-
Dexter Filmore -
Stefan Endrullis -
Timothy Pearson