i have a bot that keeps automatically opping everyone that comes in a room although i have checked and dbl checked the config. it is set as follows when i do chaninfo for that room:
Protect modes (chanmode): +tn
Idle Kick after (idle-kick): DON'T!
stopnethack: DON'T!
aop-delay: 5:30
revenge-mode: 0
ban-time: 0
exempt-time: 60
invite-time: 60
Other modes:
-inactive +statuslog -secret -shared
-greet -seen -cycle +dontkickops
-protectops -protectfriends -revenge -revengebot
-bitch -autoop -autovoice -nodesynch
-enforcebans -dynamicbans -userbans -autohalfop
-protecthalfops
-dynamicexempts +userexempts -dynamicinvites -userinvites
User defined channel flags:
-portcheck
flood settings: chan ctcp join kick deop nick
number: 21 3 3 5 5 5
time : 60 60 60 10 10 60
correct me if i'm wrong, but doesn't -autoop means not to op ppl auto?
not only does he op everyone that comes in the room, but he ops ppl who arent even in his db as users. ppl hes never even seen before. i have been trying to figure this out for a week now and i give up. please help
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
i am lost
What you need to know is that +autoop means the bot will op anyone with +o user-flag on the bot. I doubt that everyone's added on your bot as +o (this you need to check), and you also need to check if the channel is dynamically set as +autoop (regardless of what has been set in the config file). To check your channel settings use '.chaninfo #channel' and '.chanset' to modify them. Another thing that you need to consider is the possibility that you've loaded some script which is causing this behavior.
-
speechles
- Revered One
- Posts: 1398
- Joined: Sat Aug 26, 2006 10:19 pm
- Location: emerald triangle, california (coastal redwoods)
Re: i am lost
The other alternative to this is you've given any user an +a for that channel. That user would be detected strictly by the nick!ident@host.mask (host) you've entered for them. Then without a need for a password (this is how +a differs from +o) they are "automatically" opped on join forever after. You need to .match +a|+a #your-chan-here and better define the host for any user that shows up, or better yet ditch that method and just use +o and make those users use the /msg bot op pass-here way. Networks with cloaked hosts (+x) obfuscate too much of the hostmask causing collisions (incorrect host matches) to occur out of coincidence (opping the wrong person accidentally) rather than by design (a user purposely spoofs your host to attain ops on join). Using +a is a good way to lose control of your channel. Using +o even with these collisions these people must still know the password for the user they are matched incorrectly against in order to become opped.gtfo wrote:correct me if i'm wrong, but doesn't -autoop means not to op ppl auto?
not only does he op everyone that comes in the room, but he ops ppl who arent even in his db as users. ppl hes never even seen before. i have been trying to figure this out for a week now and i give up. please help
ok thanks guys.
after using the .match command i found the problem.
you guys are going to laugh, but here it is.
the owner of the room kept changing hostmasks and she had a +a flag
(y i gave channel owner +a i dunno, but...), but the bot wouldnt respond because she kept changing, so i had added *!*@*.*.*.* to cover her. well, obviously this was telling the bot to +a everyone. I simply removed the +a flag from her (she has +m and +o for the room witch should be ok) and the bot stopped opping everyone.
not a newb at computers, just a newb using eggies, so dont laugh too hard
thanks again
after using the .match command i found the problem.
you guys are going to laugh, but here it is.
the owner of the room kept changing hostmasks and she had a +a flag
(y i gave channel owner +a i dunno, but...), but the bot wouldnt respond because she kept changing, so i had added *!*@*.*.*.* to cover her. well, obviously this was telling the bot to +a everyone. I simply removed the +a flag from her (she has +m and +o for the room witch should be ok) and the bot stopped opping everyone.
not a newb at computers, just a newb using eggies, so dont laugh too hard
thanks again
yeah, well i have the channel owners set as masters in their channels and then i have ops set, or let them set their own for the channel.
there is only myself and one other person set as owners and so far that hasnt presented any problems. I set it up for ppl to use i just didnt know why he was opping everyone in that particular room until now. Clearly this is something where one needs to develop a good understanding of the flags and that is what I am doing. What would be a wise set up that you might suggest? I dont even really use the bot that much and just load whatever scripts ppl request and do whatever maintaining they cant.
there is only myself and one other person set as owners and so far that hasnt presented any problems. I set it up for ppl to use i just didnt know why he was opping everyone in that particular room until now. Clearly this is something where one needs to develop a good understanding of the flags and that is what I am doing. What would be a wise set up that you might suggest? I dont even really use the bot that much and just load whatever scripts ppl request and do whatever maintaining they cant.
I'd suggest you first remove the *!*@*... hostmask. Next add a few hostmasks matching the owner's different hosts, and tell her to try and not change hosts so much. If she really needs op/master privileges from another host, she could still use the IDENT/ADDHOST msg commands to add new hostmasks.
NML_375