What's Changed
🔧 Trusted proxy now correctly matches IPv4 addresses
Configured trusted proxies (e.g. 192.168.1.1 or 192.168.1.0/24) were never being matched. Root cause: Node.js reports IPv4 connections on dual-stack sockets as ::ffff:192.168.1.1 (IPv6-mapped format). The trust proxy callback was comparing this raw form against the configured plain IPv4 entries, so the match always failed — meaning X-Forwarded-For was never trusted and the real client IP was never used in audit logs or IP rules.
Fix: the ::ffff: prefix is now stripped before comparison, matching the same normalisation already used in the audit and session services.
Container image
docker run -d -p 7443:7443 ghcr.io/kotoxie/alterm:0.5.6