https://bz.apache.org/bugzilla/show_bug.cgi?id=69857
Bug ID: 69857
Summary: Server initiates connections to INADDR_ANY (0.0.0.0)
in mpm_unix.c
Product: Apache httpd-2
Version: 2.4.64
Hardware: HP
OS: OpenBSD
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
After upgrading from OpenBSD 7.6 to 7.7, my server error logs have been filling
up with around a thousand messages per day as follows:
[Tue Oct 21 20:32:15.637924 2025] [core:warn] [pid 962] (22)Invalid argument:
AH00056: connect to listener on 0.0.0.0:8080
This is occurring because the dummy_connection() function in server/mpm_unix.c
issues socket connections to an address it pulls from the ap_listeners list,
and if the server is configured as e.g. Listen 80, this will be INADDR_ANY
(0.0.0.0).
OpenBSD doesn't support connect() to INADDR_ANY and returns EINVAL (22).
Although other OSes have workarounds in connect(), Apache should be explicit
about the address it is trying to connect to.
In the OpenBSD 7.6 port of apr 1.7.2 there was a patch to replace the
INADDR_ANY address with the loopback address, but this actually had the
unintentional side effect of overwriting the address in the ap_listeners entry
used by dummy_connection(). It would then not be possible for Apache to tell
whether that listener was configured as Listen 80 or Listen 127.0.0.1:80.
The OpenBSD maintainers also had concerns about recent security issues on other
systems where the use of IN_ADDR_ANY has allowed security policy to be
bypassed.
For these reasons, the patch was removed for OpenBSD 7.7 so now the log files
are getting hammered, and the communication intended for ap_mpm_pod_signal()
and ap_mpm_pod_killpg() to work correctly is not occurring.
https://github.com/openbsd/ports/commit/007351bdc135b80a017ff8c3da67905ffff291e9
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
