View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001481 | unreal | documentation | public | 2004-01-10 02:46 | 2004-02-01 20:21 |
| Reporter | EviL_SmUrF2 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta19 | ||||
| Summary | 0001481: /whois error | ||||
| Description | Services Admins (services-admin;) cannot see what channels network service bots are in. odd i know. however one of my admins, if he does, lets say, a /whois elite-bot He will see this: Elite-Bot is [email protected] * Elite Elite-Bot using services.multilink User Services Elite-Bot is a Network Service elite-bot End of /WHOIS list. but i will see this: Elite-Bot is [email protected] * Elite Elite-Bot on &#mOfO.Demonic.Duelist Elite-Bot using services.multilink User Services Elite-Bot is a Network Service elite-bot End of /WHOIS list. the whole "blah is on" line is missing. he is running generic mirc, no addons or scripts of any kind. our services are anope 1.4.26 | ||||
| 3rd party modules | |||||
|
|
So you're saying admins (+A) can see it, but +a can't? |
|
|
ok i just went and tested every single oper level, and the only level that can see what channels a services bot is in is netadmin. local ircop, global ircop, server admin, co admin, and services admin cannot see what channels a services bot is in. |
|
|
that's indeed done on purpose in the source... [not saying I agree with it since it's a bit weird (at least) a services admin can't see this :p] |
|
|
Yeah it would seem to me that if you're in charge of services, you should be allowed to see what services are doing... |
|
|
i think all ircops should be able to see what rooms a services bot is in. why not? lol not like its a big security problem heh |
|
|
The only problem with allowing to see what channels a service bot is on, is when it comes to networks that make 'ChanServ' join all channels that are registered. on a largish network, this could be for some large reply... restricting it to service admin or better would be the way.. |
|
|
eh, nah, local ircop and up i think would be good. |
|
|
Now that I'm thinking about it, I'm not sure why _anyone_ needs to see this information. |
|
|
we use it so that we can trim the botserv list from time to time from opers who make a botserv bot, plop it in a channel, then the channel is dropped and the bot sits there idling on the network for weeks on end not even in a channel. |
|
|
So you mean you look for the bots that are not in any channels? Also, any oper is allowed to create/delete botserv bots? It's not restricted to +a? |
|
|
-BotServ- The following command is available to Services admins: - -BotServ- - -BotServ- BOT Maintains network bot list - yeah its limited to services admins. but users will request a bot, we'll make it for them, drop it in their channel, then 2 weeks later they'll drop the chan and the bot will sit on the network idling lol. itd be helpful it locops and up can see what channels a network service is in. |
|
|
Fixed in CVS. services admins and netadmins can now view it. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-01-10 02:46 | EviL_SmUrF2 | New Issue | |
| 2004-01-10 05:37 |
|
Note Added: 0004588 | |
| 2004-01-10 06:54 | EviL_SmUrF2 | Note Added: 0004598 | |
| 2004-01-10 13:36 | syzop | Note Added: 0004600 | |
| 2004-01-10 16:23 |
|
Note Added: 0004603 | |
| 2004-01-10 19:20 | EviL_SmUrF2 | Note Added: 0004606 | |
| 2004-01-10 20:35 | Praetorian_ | Note Added: 0004607 | |
| 2004-01-11 11:14 | EviL_SmUrF2 | Note Added: 0004631 | |
| 2004-01-11 15:29 |
|
Note Added: 0004632 | |
| 2004-01-11 18:09 | EviL_SmUrF2 | Note Added: 0004636 | |
| 2004-01-11 19:43 |
|
Note Added: 0004637 | |
| 2004-01-11 22:08 | EviL_SmUrF2 | Note Added: 0004651 | |
| 2004-02-01 20:21 | syzop | Status | new => closed |
| 2004-02-01 20:21 | syzop | Note Added: 0004849 |
