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

Prevent Eggdrop from adding bot with same botnet-nick as self #424

Open
vanosg opened this Issue Jul 14, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@vanosg
Collaborator

vanosg commented Jul 14, 2017

Example:

.whoami
You are -HQ@scooby.

.+bot scooby 192.168.180.136 3183  <<Edit: This is the IP of a different bot named scooby>>
Added bot 'scooby' with address [192.168.180.136]:3183/3183 and no hostmask.
You'll want to add a hostmask if this bot will ever be on any channels that I'm on.

.link scooby
Link to myself?  Oh boy, Freud would have a field day.

The closest thing I can think of as a use case is something perhaps to do with userfile sharing. What do we think- should we prevent the user from doing this, or no?

@maimizuno

This comment has been minimized.

Show comment
Hide comment
@maimizuno

maimizuno Jul 16, 2017

Since they couldn't exist together on the same botnet, beign able to ".relay" to two bots with the same [botnet-]nick doesn't seem like that useful of a ability [and is confusing as hell].

I vote: block it (not that you wanted MY opinion)

maimizuno commented Jul 16, 2017

Since they couldn't exist together on the same botnet, beign able to ".relay" to two bots with the same [botnet-]nick doesn't seem like that useful of a ability [and is confusing as hell].

I vote: block it (not that you wanted MY opinion)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment