View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003321 | unreal | ircd | public | 2007-05-07 20:38 | 2007-05-08 03:53 |
| Reporter | Shining Phoenix | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.6 | ||||
| Summary | 0003321: Make CIDR a party of banmasks | ||||
| Description | I know that there is a module that provides the ~C extban to do this, but not using an extban at all would be better. Then we could get bans looking like this: +b *!*@adf345.865ecb.45dcd2/124 +b ~n:*!*@adf345.865ecb.45dcd2/124 instead of: +b ~C:*!*@adf345.865ecb.45dcd2/124 +b ~n:~C:*!*@adf345.865ecb.45dcd2/124 The / and CIDR range at the end would be removed if the target has usermode t. | ||||
| 3rd party modules | |||||
|
|
How will you know which CIDR to set with a cloaked host? How will Unreal know what network a cloaked host belongs to? What use would this be to the common user? |
|
|
You can already do a proper thing by the style of cloaking for ips.. the host is something like .. hash(a.b.c.d) + "." + hash(a.b.c) + hash(a.b), making it possible to ban on /16, /24, and /32 |
|
|
See stskeeps comment, no weird cloaking stuff needed. As for CIDR for bans, see 0002870. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-05-07 20:38 | Shining Phoenix | New Issue | |
| 2007-05-08 01:00 | Stealth | Note Added: 0014034 | |
| 2007-05-08 03:44 |
|
Note Added: 0014041 | |
| 2007-05-08 03:44 |
|
Status | new => feedback |
| 2007-05-08 03:53 | syzop | Status | feedback => closed |
| 2007-05-08 03:53 | syzop | Note Added: 0014042 | |
| 2007-05-08 03:53 | syzop | Resolution | open => no change required |
