Skip to content
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.

Clientbot message handling is prone to nick collisions #327

Closed
jlu5 opened this issue Sep 2, 2016 · 1 comment
Closed

Clientbot message handling is prone to nick collisions #327

jlu5 opened this issue Sep 2, 2016 · 1 comment
Assignees
Labels
involves: security issues related to security protocol: clientbot type: bug involves a bug or bug fix

Comments

@jlu5
Copy link
Collaborator

jlu5 commented Sep 2, 2016

No description provided.

@jlu5 jlu5 added type: bug involves a bug or bug fix protocol: clientbot labels Sep 2, 2016
@jlu5 jlu5 added this to the v1.0 (previously 0.10.x) milestone Sep 3, 2016
jlu5 pushed a commit that referenced this issue Sep 7, 2016
…real users in Clientbot

For #327. Essentially what this does is tack on a nick prefix to all service bots introduced on a Clientbot network, using characters invalid for regular nicks.
@jlu5 jlu5 closed this as completed Sep 10, 2016
@jlu5 jlu5 changed the title Virtual service bot generation on Clientbot may be prone to nick collisions Clientbot message handling is prone to nick collisions Oct 15, 2016
@jlu5 jlu5 reopened this Oct 15, 2016
@jlu5
Copy link
Collaborator Author

jlu5 commented Oct 15, 2016

This affects way more than just services bots. Anything prone to nick collisions will cause messages to be routed through the wrong source.

jlu5 pushed a commit that referenced this issue Oct 15, 2016
@jlu5 jlu5 closed this as completed in 405b886 Oct 15, 2016
@jlu5 jlu5 self-assigned this Oct 15, 2016
@jlu5 jlu5 added the involves: security issues related to security label Dec 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
involves: security issues related to security protocol: clientbot type: bug involves a bug or bug fix
Projects
None yet
Development

No branches or pull requests

1 participant