[stunnel-users] inetd mode endpoint count check

• Previous message (by thread): [stunnel-users] inetd mode endpoint count check
• Next message (by thread): [stunnel-users] fix resource leaks and potential null
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Michael,

Your configuration does not make sense.  You cannot use stdin/stdout *and* connect *and* exec at the same time.

I guess what you want is a connect+exec service. You need to define a service section for it.

Please read the fine manual about inetd mode of stunnel configuration. I don't think this is what you want to use.

Mike

Michael Weiser <michael at weiser.dinsnail.net> wrote:

>Hello,
>
>a client setup such as this:
>
>client = yes
>foreground = yes
>connect = example.com:80
>exec = cat
>execargs = cat
>
>causes stunnel-4.54 to fail with error:
>
>Service [stunnel]: Inetd mode must define one endpoint
>
>The attached patch fixes the problem for me. Dunno if the endpoint
>check
>is too lax for other cases then, though.

• Previous message (by thread): [stunnel-users] inetd mode endpoint count check
• Next message (by thread): [stunnel-users] fix resource leaks and potential null
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]