View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000954 | unreal | ircd | public | 2003-05-06 08:00 | 2003-05-29 02:38 |
| Reporter | dj4aces | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Summary | 0000954: snomasks for vhost | ||||
| Description | On the network I'm on, we have what's called a User Commitee, which keeps tabs on the operators, and which operators may/may not be abusing their o:lines. I'd be interested in seeing the ability to grant those on the user commitee the ability to utilise specified snomasks, so they can keep tabs on the operators, as well as assist with spotting bot floods and the like, without actually having an o:line. This is because, currently, the only way to give these esteemed users the ability to utilise snomasks is by giving them, at least, a local o:line - which could is not in our best interest. This could be specified similar to how snomasks are specified in the oper block in the conf file. It wouldn't just give the users who have vhosts snomasks by default. I'm hoping you guys could code this, because currently, the User Commitee members have no way of seeing this stuff, unless we paste it to them. This can become very troublesome - especially when it floods the channel with akills, glines, and the like. Thanks for listening/viewing, and I definitely hope you all implement this in future versions of the ircd. | ||||
| 3rd party modules | |||||
|
|
How about a powerless o:line/oper block? It isn't possible to have a powerless o:line at the moment because alot of the flags are included by default (which seems to defeat the purpose of having the flags in the first place) |
|
|
Currently there are lot's of Is(An)Oper() checks, so.. just an oper check, not a special operflag check.. so that powerless o line is too hard ;). And about snomasks, currently they are stripped down to +s +sk (or something) for normal users, would require the code to be changed at several places. Then again, maybe you also want to receive GLOBOPS etc... ;p. What about a bot which /oper's and receives + forwards these messages to a channel with key (+k) or something... :P. |
|
|
Yes, I noted the +s +sk snomasks for normal users before I got my o:line. What I'd like to do is something like this: vhost { vhost usercom.zirc.org; login nickname; password password; swhois "is a UserCom Member"; snomask cfkevGq; }; This would require said usercom member to /vhost nickname password in order to receive notices only IRC operators traditionally receive. This would not only help identify particular problems to the commitee members, but would also help get said users ready to become an IRC operator. I'm not sure of the difficulty of the above, I'm just grasping at straws. I thought it would be an excellent idea for the network, and perhaps other networks, should they wish to set something like this up for themselves. |
|
|
yes I understood that already, I usually don't reject feature requests, but this one is very specific for your net and makes the code much more complicated / waste of memory (coders: since I guess we have to "remember" the vhost struct to see which one's are allowed to set it has to be in the [user] struct, etc...), that's why I suggested the bot. I won't code it (for free ;p), dunnow about other coders... |
|
|
I understand this, really. I didn't know if it would be considered, I just thought it would be a cool feature to implement - whether it be for our network, or just something that everyone could play with. Thanks for your time, though. Perhaps one of the other coders could, if nothing else, attempt it. If not, I'm just happy that I received a response :D |
|
|
The purpose of vhost {} is to set a vhost, not to set snomask values. If you want something like that, Unreal supports modules, create a /usercomm command that gives the user the flags... |
|
|
I just don't see the point of having some of these flags (can_kline, can_rehash etc) if they are given by default anyway, with no way of limiting the oper so (s)he can't have certain flags, but can have others. |
|
|
As codemastr said, vhost blocks aren't ment for that. Ofcourse if you really want such a feature you could have the feature coded for money ([email protected]), which is quite normal for such network-specific features :p. Do whatever you want :). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-05-06 08:00 | dj4aces | New Issue | |
| 2003-05-06 17:51 | Joolz | Note Added: 0002669 | |
| 2003-05-06 18:41 | syzop | Note Added: 0002670 | |
| 2003-05-06 19:30 | dj4aces | Note Added: 0002673 | |
| 2003-05-06 21:11 | syzop | Note Added: 0002674 | |
| 2003-05-06 21:24 | dj4aces | Note Added: 0002676 | |
| 2003-05-06 21:44 |
|
Note Added: 0002682 | |
| 2003-05-06 23:45 | Joolz | Note Added: 0002685 | |
| 2003-05-29 02:38 | syzop | Status | new => closed |
| 2003-05-29 02:38 | syzop | Note Added: 0002863 |
