Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#74 kill & kick crossing + rejoin => protocol violation

u2.10.12
open
nobody
Protocol (20)
5
2005-11-05
2005-10-05
coekie
No

A kill (or collision) and a kick crossing eachother can
cause protocol violations.

For example:
On server1, user1 and user1b are (the only ones) in
#foo. user2 is a user on server2.
At the same time (so the 2 events cross eachother)
user1 kicks user1b and user2 kills (or nick collides with)
user1b. Now server2 just ignores the kick it receives
(because the kicker doesn't exist anymore), and thinks
user1 is still on #foo.
If user1 now joins the channel again, server2 sends a
wallop: Protocol Violation from user1: user1 tried to
CREATE a channel already joined.

Discussion

  • Reed Loden
    Reed Loden
    2005-11-05

    • labels: --> Protocol
     
  • Reed Loden
    Reed Loden
    2005-11-05

    • milestone: --> u2.10.12
     
  • Logged In: YES
    user_id=65117

    coekie means that user2 kills or collides with user1, not user1b.

    I can't see a good way of dealing with this...short of commenting out the protocol violation or just pulling the database out of ircu entirely, at least.