View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006395 | unreal | ircd | public | 2024-03-23 16:32 | 2024-07-09 16:21 |
| Reporter | Valware | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0006395: Please add the possibility for using set <security group>::restrict-commands | ||||
| Description | It would be super cool to be able to restrict commands per security-group. Example: <code>
set unknown-users {
restrict-commands {
list { except { identified yes; } }
private-message { except { identified yes; } }
private-notice { except { identified yes; } }
}
}
</code> | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
The ::except item is a Mask item, so you can already use security-group there. https://www.unrealircd.org/docs/Mask_item But what you suggest is possibly more intuitive. Although I am not 100% sure if it wouldn't be more confusing in the end if you have like multiple security group matches, skipping the original set block, having security group selectors within this suggestion.. etc... but will think about it! |
|
|
Well, I do like the fact you can use a mask item in the security-group block so you can match other security-groups. � |
|
|
Seconded |
|
|
A scenario came up today where this would be the only method I can think of to achieve their goal. The scenario being to restrict use of JOIN for a delay after connect but only for a small subset of users based on IP address masks. The restrict-commands::except::connect-time option would provide the delay, but then how would you limit that to only be applied to users matching a specific IP mask? |
