Note that stunnel died completely.. I.e. not just denied the new connection..
It might be something with my environment of course.
FreeBSD 4.4 , Stunnel 4.05 ( died ) FreeBSD 4.11-p12 , Stunnel 4.11 ( died )
Disabled libwrap and everything worked fine..;-)
If this is the intended action then there is a good possibility for killing stunnel daemons out there.. i.e. if someone sets up tcpwrap to only allow some connections....
/Uffe
Jan Meijer wrote:
On Fri, 14 Oct 2005, Uffe Vedenbrant wrote:
Jan Meijer wrote:
On Fri, 14 Oct 2005, Uffe Vedenbrant wrote:
Is there any possibility to have stunnel to say something about tcpwrapper problems..;-)
I don't really understand it as I made this config error a couple of times myself but it was nicely logged. Then again, this last happened to me with 3.x code so...
Was it logged by tcpwrapper (libwrap) or by stunnel that logged your problems?
I wouldn't know anymore. Would have to test/check the code, but without doubt Mike already knows the answer.
Jan