I was reading a book where they discussed using stunnel as client and server proxy with -d -r and -c options. I have SuSE 9.3 and the stunnel on it has different options. Then I found that we have to use config file. I used it to configure my server. I defined the following section:
[myserver] accept = 12345 connect = 12323
Here my server listens on 12323. I have my server already running. Now I typed stunnel and nothing happened. I typed "pgrep stunnel" and could not see anything. Apparently I have not understood how stunnel works. Can some one let me know how can I configure to use stunnel to secure my server app and my client app which are not ssl aware.
I also have a question. The book which I am reading says, stunnel acts as a proxy for a server app. If my server app is listening on A then if I want stunnel to service all clients connecting to A then how can it do it as that port is already serviced by my server app.
Thanks JB
"Jagannadha Bhattu" jagannadha.bhattu@gmail.com wrote:
Now I typed stunnel and nothing happened.
Check your log files.
grep stunnel /var/log/syslog | tail
Apparently I have not understood how stunnel works.
Did you read the fine manual? http://stunnel.mirt.net/static/stunnel.html
There are some great examples gathered by Brian Hatch: http://www.stunnel.org/examples/
Best regards, Mike