From:
[email protected]
On Di, 2004-08-10 at 11:40, Andras Korn wrote:
we run bopm on one of the Hungarian IRCNet servers. Unfortunately, it often segfaults. Investigating the segfaults, we found that they seem to happen when a user connects from a host that only has an AAAA and no A record (possibly the mere existence of an AAAA record is enough to trigger the
bug).
The only way to crash BOPM is passing wrong data through the CONNREGEX.
As BOPM depends on the IP being present in the notices your ircd is
probably the root of this problem. It reports wrong IPs (in this case
probably none at all -- just DNS names) which cause BOPM to crash.
There is no support of IPv6 planned in BOPM, also because of the lack of IPv6-capable proxies. There are no known IPv6 abuses by now.
You probably have to modify your IRCd to give out slightly changed
connection notices -- which do not match upon the CONNREGEX -- when no
IPv4 address is available.
All hacks to modify BOPM to resolve the requests on its own are
unsupported upstream, and also on Debian.
Regards,
Philipp Kern
Blitzed IRC Network
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)