#1905 - IP bans are broken for manual wildcard bans
-
By Jason Verhagen
- Added
- 0 views
| Identifier | #1905 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | IP bans are broken for manual wildcard bans |
| Status | Completed |
| Handling member | PDStig |
| Addon | General / Uncategorised |
| Description | Running Composr v9.0.19, IP Bans from Adminzone>Security>Banned IP Addresses generates warnings for all IPv4 addresses that contain an asterisk wildcard when the Save button is clicked. It also generates a warning for an auto-banned IPv6 address. The warnings say the IP addresses are not valid. Here are two example warnings:
'A ban on 120.40.145.* could not be added, as the IP address is not valid (must must be a full IPv4 or IPv6 address).' 'A ban on 2a00:1210:fffe:0196:0000:0000:0000:0001 Failed to complete the CAPTCHA while posting links in unrecognised Comcode-syntax (silent error to catch spammers) could not be added, as the IP address is not valid (must must be a full IPv4 or IPv6 address).' |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
Banning of wildcard addresses, and ipv6 addresses are not working when done manually via the IP ban management screen.