Read a trusted_proxies entry in the IPv4-mapped form as its IPv4 range (closes #303) #305

Merged
clawbot merged 2 commits from issue-303-mapped-trusted-proxies into next 2026-10-19 05:29:06 +02:00
2 Commits
Author SHA1 Message Date
clawbot a14c5a1ba0 Read a trusted_proxies entry in the IPv4-mapped form as its IPv4 range (closes #303)
check / check (push) Waiting to run
The client address is matched against trusted_proxies as the IPv4 address
an IPv4-mapped address holds, so an entry such as ::ffff:10.0.0.0/104
trusted nothing. parseCIDRList, which reads both trusted_proxies and
blocked_networks, now keeps such an entry as the IPv4 range it covers and
refuses one shorter than /96 naming the setting it reads.
parseBlockedNetworks, which did this for blocked_networks alone, is gone.

Model: opus-5-5
2026-10-19 03:02:23 +00:00
clawbot 2c0fc688f9 Test that a trusted_proxies entry in the IPv4-mapped form is read as its IPv4 range
These tests fail on next: ::ffff:10.0.0.0/104 is kept as written and so
never matches, and ::ffff:0:0/95 loads without an error. The fix follows
in the next commit.

Model: opus-5-5
2026-10-19 03:02:01 +00:00