Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

skeleton enforcement for channels? #581

Closed
slingamn opened this issue Jul 1, 2019 · 1 comment
Closed

skeleton enforcement for channels? #581

slingamn opened this issue Jul 1, 2019 · 1 comment
Assignees
Milestone

Comments

@slingamn
Copy link
Member

slingamn commented Jul 1, 2019

We don't enforce the uniqueness of channel name skeletons, should we?

I haven't considered this as much of a priority because INVITE and LIST seem like the only contexts in which one might spoof a channel name (in contrast to which, nick spoofing is a potential issue whenever you're receiving a PRIVMSG).

@DanielOaks
Copy link
Member

Hum. Yeah we should be doing this as well. Channel registration as well to ensure unique skeletons are registered probably.

@slingamn slingamn added this to the v1.2 milestone Jul 1, 2019
@slingamn slingamn modified the milestones: v1.2, v1.3 Nov 8, 2019
@slingamn slingamn self-assigned this Dec 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants