i have a question:
I conbfigure the stunnel to work as tcp wrapper. I configure stunnel for accept on 2003 and connect to 10.1.1.1:2003 (not exist address).
I see that any TCP connect to 2003 always succeed. I expect that the TCP connect will fail if the remote side connection failed.
Is there a way to make it happen
Nadav Erez R&D Verint Systems Inc Phone: +972+9-9624753 Cellular: +972-54-7784753 Email: Erez.Nadav@verint.com Web: www.verint.com http://www.verint.com/
__________________________________________________________________________________________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1).
There's no way to know with BSD sockets details of the connection to be accepted (for access control) without actually accepting it.
Best regards, Mike
_____
From: stunnel-users-bounces@mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Nadav, Erez Sent: Tuesday, December 27, 2005 3:29 PM To: stunnel-users@mirt.net Subject: [stunnel-users] stunnel connect success even if remote side do notexist
i have a question:
I conbfigure the stunnel to work as tcp wrapper. I configure stunnel for accept on 2003 and connect to 10.1.1.1:2003 (not exist address).
I see that any TCP connect to 2003 always succeed. I expect that the TCP connect will fail if the remote side connection failed.
Is there a way to make it happen
Nadav Erez R&D Verint Systems Inc Phone: +972+9-9624753 Cellular: +972-54-7784753 Email: Erez.Nadav@verint.com Web: www.verint.com http://www.verint.com/
____________________________________________________________________________ ______________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1).