fedserv/echoIRCd
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

extbanbanlist: identify extbans by the real rule (<letter>:...) instead of "2nd byte is a colon" — the old heuristic wrongly skipped a plain hostmask whose second char happened to be ':', mis-listing it

Browse source
This commit is contained in:
Jean Chevronnet 2026-08-19 01:18:27 +00:00
parent 6f9d11f83e
commit 924141683c
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/modules/extbanbanlist.rs
View file

@ -10,9 +10,11 @@ use crate::channels::glob_match;
use crate::server::Server;
use crate::Uid;
/// A plain host-mask ban entry (not itself an extban).
/// A plain host-mask ban entry (not itself an extban). An extban is `<letter>:…`,
/// matching `normalize_ban_mask`'s rule — anything else is a plain host-mask.
fn is_plain(mask: &str) -> bool {
mask.as_bytes().get(1) != Some(&b':')
let b = mask.as_bytes();
!(b.len() >= 2 && b[0].is_ascii_alphabetic() && b[1] == b':')
}
/// True if `uid` is on `chan`'s (plain) ban list with no matching plain exception.