Bug#949779: stunnel4: fails to work as client when stdin is a pipe

Dixi quod… >>This is a showstopper for using stunnel in client mode… Hrm… doing it like this works; I was deep in yak shaving and probably should have thought of this earlier: $ { cat a; sleep 1; } | stunnel4 x Basically, I was chasing a lot of issues at the same time. If you don’t see

Bug#949779: stunnel4: fails to work as client when stdin is a pipe

Control: notfound -1 3:4.29-1+squeeze1 Thorsten Glaser dixit: >$ cat a | stunnel4 x >$ stunnel4 x This is a showstopper for using stunnel in client mode… The client configuration looks like this: client = yes connect = host:port socket = r:SO_KEEPALIVE=1 socket = r:TCP_KEEPCNT=4 socket =

Bug#949779: stunnel4: fails to work as client when stdin is a pipe

Package: stunnel4 Version: 3:5.56-1 Severity: important Watch this: $ cat a GET /cgi-bin/conninfo.cgi HTTP/1.0 Host: XXX $ cat a | stunnel4 x $ stunnel4 x https://www.stunnel.org/pipermail/stunnel-users/2009-January/002223.html This is a showstopper for using stunnel in client mode… --