Description of Problem:
If tcp_wrappers is disabling access to a service then the message in syslog
looks like it is comming from the calling application. When the application
itself also has Access Control measures this usually causes confusion.
Version-Release number of selected component (if applicable):
This only needs to be a simple cosmetic change in the syslog message, making it
obvious that the message originated from the libwrap.a code and not the
The application, which is using tcp_wrappers, should not generate
Applications like apache, samba, rsyncd and snmpd all have their own
access controls. So what are you saying ... that they should never be
used or that if they fail they should never be logged?
The application is not logging (should not log) the same errors or
restrictions as tcp_wrappers does, so there is no conflict. This is
what I tried to say.
By the way: If I modify the log message, then some programs (eg. log
analyzers) have problems with this. It is not useful to make it
incompatible to them.