Sujet : Re: inn, cleanfeed and ipv6
De : info (at) *nospam* tcpreset.invalid (Gabx)
Groupes : news.software.nntpDate : 09. Apr 2025, 13:47:42
Autres entêtes
Organisation : Victor Hostile Communication Center
Message-ID : <vt5q9f$1342t$1@news.tcpreset.net>
References : 1
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 SeaMonkey/2.53.20
noel wrote:
I've had a few reports of select users posts not getting out to all
servers, and experienced it myself in a group last night, running one of
my scripts that checks open servers, verified my suspicions, there seems
to be something in the cleanfead script inn servers not liking (all?)
ipv6 addresses.
This is excerpted from cleanfeed
if ($hdr{'Injection-Info'} =~ /^$hws*($Hostname)[ \t;]/) {
$state{injection_host} = "$1"
} elsif ($hdr{'X-Trace'} =~ /^$hws*($Hostname)$hws/) {
$state{injection_host} = "$1"
} else {
$state{injection_host} = first_path_host($hdr{Path});
};
The pattern defined in $Hostname is designed to match traditional hosts – composed of letters, numbers and dots – or IPv4 addresses.
However, IPv6 addresses, which include hexadecimal characters and the “:” character, do not fall into this set.
So, if an Injection-Info header contains an IPv6 address (e.g. “2a01:4f8:c0c:2f94::1”), the regex will not match it correctly.
Gabx