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

Support for super users #45

Open
numberten opened this issue Jul 1, 2014 · 5 comments
Open

Support for super users #45

numberten opened this issue Jul 1, 2014 · 5 comments

Comments

@numberten
Copy link
Owner

I think we should add some formal support for 'super users' or higher tiered users. This would allow for things like #44. Any ideas for a good way of doing this?

I was thinking a nice way of doing this would be passing a list of approved nicks as command line args and storing them as bot state accessible to any component. I'm unsure how nick clusters would be treated though. Not respecting clusters would be annoying, but respecting them could be a security hole.

@fimad
Copy link
Collaborator

fimad commented Jul 1, 2014

I don't think we should obey nick clusters for super users. Too easy to game.

I think the most extensible way to do this would be like the list component. Super user nicks are stored in a data file and there is a privileged command to add and remove users from that list.

@numberten
Copy link
Owner Author

👍

@numberten
Copy link
Owner Author

How do the first super users get authenticated? Manually editing the data/superusers file before your first run is kinda janky.

@fimad
Copy link
Collaborator

fimad commented Jul 1, 2014

Couple of ideas, not sure if any are good.

  1. Automatically add a nick to the file if they are op and they grant ops to the bot.
  2. When joining a channel, automatically add all ops to the list of super users for that channel.
  3. Set a password as a command line flag. Anyone who pm's zbot the password gets added to the list of super users.

@numberten
Copy link
Owner Author

The first two would work well on a ChanServ registered channel (so on freenode) where you don't automatically become an op by being the first one to connect in a channel. Probably not so good for other ircds or unregistered channels.

I really like 3 though, I think that would work well.

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

No branches or pull requests

2 participants