STUNNEL WINDOWS 7 INSTALL
STUNNEL WINDOWS 7 64 BIT

I just modified the example that comes with Stunnel. This seems extremely complicated for me but I really would like to keep using OE if at all possible. Is there a proxy out there which will do the same thing for me without having to run a proxy myself? I think this would be the ideal solution if possible.

STUNNEL WINDOWS 7 64 BIT

Is this correct? Can this proxy be installed in the same machine or does it need to go in another machine? If it needs to go in another machine I was thinking of installing it in my Linux machine so that OE would connect to the proxy on the Linux machine which would then connect to the real servers.Īnother thing is that in the STunnel download page I only see 64 bit versions so that would preclude installing it on the same WIN XP machine as that is 32 bit.

STUNNEL WINDOWS 7 INSTALL

That page says the only work-around is to install STunnel which is a proxy so that OE can connect to the proxy and the proxy can the connect to the email servers using the required TLS protocol. That is what I gather from this page and I would like to confirm I understood that right. If I understand the issue correctly the outlook/hotmail servers now require some kind on encryption that OE does not support. After some investigation it seems MS had changed the POP3 and SMTP servers and, crucially, the encryption scheme. Well, from yesterday my MS Hotmail accounts have stopped working with OE even though my GMail and other accounts are still working.

I know it is old, outdated, deprecated, unwanted, unloved, despised, etc. The peer-certificate.pem file needs to contain the server certificate.I have been using MS Outlook Express as an email client for over 20 years now. The following configuration requires stunnel version 4.46 or higher: The ca-certs.pem file contains the certificates of trusted certificate authorities.Īlternatively, a technique known as certificate pinning can be used. The following configuration requires stunnel 5.15 or later: Stunnel can use an existing PKI (Public Key Infrastructure). The 'key' option may be omitted if cert.pem also contains the private key. A certificate can also be purchased from one of the available commercial certificate authorities. On Unix platforms, a certificate can be built with 'make cert'. The Windows installer of stunnel automatically builds a certificate. Unless PSK authentication is configured, each stunnel server needs a certificate with the corresponding private key. The advantage of this configuration is that it does not require individual secrets for each of the clients. Certificatesįor simplicity, this tutorial only covers server authentication.

Otherwise, all the clients sharing the same key will have to be reconfigured if the key is compromised.

The psk1.txt file only needs a single line: test1:oaP4EishaeSaishei6rio6xeeph3azĮach client needs a separate secret. The psk.txt file contains one line for each client: test1:oaP4EishaeSaishei6rio6xeeph3az Server ConfigurationĪ trivial configuration example: PSK authentication requires stunnel version 5.09 or higher. PSK is also the fastest TLS authentication. It provides both client and server authentication. The easiest way to configure authentication is with PSK (Pre-Shared Key).

Client authentication allows for restricting access for individual clients (access control).

Server authentication prevents Man-In-The-Middle (MITM) attacks on the encryption protocol.

Either the TLS client, the TLS server, or both need to be authenticated:

Stunnel windows 7