| Summary: | Kopete IRC module answers to CTCP LAG, which makes Kopete appar to be infected by a CatcherTrojan | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Stefan Fiedler <stefan.fiedler> |
| Component: | IRC Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Stefan Fiedler
2005-11-22 21:34:14 UTC
OK, while the CTCP specs I've found (http://www.invlogic.com/irc/ctcp.html#4) state that: Requests which are not recognised or are invalid may return an error message similar to the following: NOTICE <space> <target> <space> : <marker> ERRMSG \ <command> [<arg> [...]] <marker> It seems that NONE of the IRC clients out there* respond to bogus CTCP requests. I guess we should change our behaviour to match the other clients. *) I tried: Gaim, irssi, xchat, ircII, BitchX, epic4, mIRC *** Bug has been marked as fixed ***. |