Bug 149540

Summary: whois storm on channel join causes flood kill
Product: [Unmaintained] kopete Reporter: Will Stephenson <wstephenson>
Component: IRC PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kde-bugs
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Will Stephenson 2007-09-04 17:35:00 UTC 
Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs

From https://bugzilla.novell.com/show_bug.cgi?id=272855

I don't have time to fix this.

"In today's status meeting, I was kicked several times again.

After the meeting, I tried again (just entered the channel, didn't write
anything) and was kicked within a minute - this time with wireshark watching
the line. I'll send you a tcpdump via mail (because it could contain private
data).
You can get a quick overview of what Kopete is doing by "parsing" the file with
"strings" or look at the packages in detail (including timestamps) by opening
it in wireshark.

As far as I can see, Kopete does lots of WHOIS requests, which the server
obviously doesn't like.
Reducing the frequency of the WHOIS requests would be interesting to test...

The package is nearly up to date:
# rpm -qf --last `which kopete`
kdenetwork3-InstantMessenger-3.5.7-25.4        Mi 18 Jul 2007 00:34:17 CEST
"
Comment 1 Christian Boltz 2007-09-05 19:42:01 UTC 
I'm the initial reporter and my offer to send you a tcpdump is still valid - just drop me a mail.
Comment 2 Justin Zobel 2021-03-09 22:41:01 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Christoph Cullmann 2024-09-18 18:28:05 UTC 
Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.