2 secure sockets TCP (Server / Client) as posted earlier last month by khaled - stunnel-users

4 Feb 2008

...
Hi,
I'm having the same question (and problem) as posted by khaled on Mon
Jan 7 19:31:03 CET 2008, subject [stunnel-users] 2 secure sockets TCP
(Server / Client).
I think I have to send data to stunnel on the client side by a write
to localhost:1974 where stunnel is configured with this stunnel.conf:
; Sample stunnel configuration file by Michal Trojnara 2002-2006
; Some options used here may not be adequate for your particular
configuration
; Certificate/key is needed in server mode and optional in client mode
; The default certificate is provided only for testing and should not
; be used in a production environment
cert = stunnel.pem
;key = stunnel.pem
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
; Use it for client mode
;client = yes
; Service-level configuration
[sip2s]
accept = 1975
connect = 127.0.0.1:1974
To start stunnel only works with just stunnel.
Started from batch or in dos-box with the options -d -r etc. as
explained in the documentation does not work, error message: file not
found)
BTW: I'm using Windows XP Professional on both client and server.
Client IP = 10.4.208.159, server IP = 10.4.208.102 for a test set-up.
On the server side it gives the same error when started with options.
stunnel.conf on the server is this:
; Sample stunnel configuration file by Michal Trojnara 2002-2006
; Some options used here may not be adequate for your particular
configuration
; Certificate/key is needed in server mode and optional in client mode
; The default certificate is provided only for testing and should not
be used in a production environment
cert = stunnel.pem
;key = stunnel.pem
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
; Some debugging stuff useful for troubleshooting
debug = 7
output = stunnel.log
; Use it for client mode
client = yes
; Service-level configuration
[sip2s]
accept = 1975
connect = 127.0.0.1:1974
Reading data on TCP/IP 1974 does not display anything when the client
is sending data to localhost:1974 which is encrypted by stunnel an
forwarded on TCP/IP 1975.
At least that is my intention, but something I do is wrong.
Data sending unencrypted between client an server works fine, so
connection is possible.
Any idea what I should do to let it work like this:

a client sends data to a server and reads the response from this

server.

all data on the network between client an server should be