On Wed, 2021-04-14 19:45:06 +0200, Jorge Redondo Flames wrote:
Stunnel could listen on its local port *only* when the peer server is listening on its corresponding server socket. So if there is no serve on the other side, there should not be local listening socket. Does not that make sense?
Stunnel connects to the server only when a client connects to Stunnel. If Stunnel is not listening for clients, it does not try to connect to the server. If it does not try to connect to the server, it does not know if the server is listening.
Ludolf
On Wed, 14 Apr 2021 at 19:38, Ludolf Holzheid lholzheid@bihl-wiedemann.de wrote:
On Wed, 2021-04-14 19:13:03 +0200, Jorge Redondo Flames wrote:
[..]
Is there a way to configure Stunnel to *close* the local socket (not listening anymore) whenever the peer process (i.e. the server) has closed its socket?
Stunnel listens for connection request from the client(s) and connects to the server on behalf of the client(s). How will a client ever be able to connect through Stunnel again if Stunnel closes the listening socket?
Ludolf
Then here I see a design flaw unless being as transparent as possible is not a goal for stunnel: “Stunnel connects to the server only when a client connects to Stunnel”. Why not listening only when the server, known beforehand from configs, is listening?
On Wed, 14 Apr 2021 at 20:01, Ludolf Holzheid lholzheid@bihl-wiedemann.de wrote:
On Wed, 2021-04-14 19:45:06 +0200, Jorge Redondo Flames wrote:
Stunnel could listen on its local port *only* when the peer server is listening on its corresponding server socket. So if there is no serve on the other side, there should not be local listening socket. Does not that make sense?
Stunnel connects to the server only when a client connects to Stunnel. If Stunnel is not listening for clients, it does not try to connect to the server. If it does not try to connect to the server, it does not know if the server is listening.
Ludolf
On Wed, 14 Apr 2021 at 19:38, Ludolf Holzheid <
lholzheid@bihl-wiedemann.de>
wrote:
On Wed, 2021-04-14 19:13:03 +0200, Jorge Redondo Flames wrote:
[..]
Is there a way to configure Stunnel to *close* the local socket (not listening anymore) whenever the peer process (i.e. the server) has
closed
its socket?
Stunnel listens for connection request from the client(s) and connects to the server on behalf of the client(s). How will a client ever be able to connect through Stunnel again if Stunnel closes the listening socket?
Ludolf
--
Ludolf Holzheid
Bihl+Wiedemann GmbH Floßwörthstraße 41 68199 Mannheim, Germany
Tel: +49 621 33996-0 Fax: +49 621 3392239
mailto:lholzheid@bihl-wiedemann.de https://www.bihl-wiedemann.de
Sitz der Gesellschaft: Mannheim Geschäftsführer: Jochen Bihl, Bernhard Wiedemann Amtsgericht Mannheim, HRB 5796
Datenschutzerklärung: https://www.bihl-wiedemann.de/de/meta/datenschutz _______________________________________________ stunnel-users mailing list -- stunnel-users@stunnel.org To unsubscribe send an email to stunnel-users-leave@stunnel.org
-
Jorge Redondo Flames -
Ludolf Holzheid