stunnel-4.04.exe) is the actual stunnel program and NOT a self-extracting exe program. Place everything in the same directory, e.g. If in doubt what you need, download the latest stunnel binary as well as the ZIP file with the openssl libararies. Copy the files to a location of your choice. These are distributed as binaries at – download your copy before proceeding. You can fully utilize your stunnel knowledge on Windows, because there is an excellent and fully equivalent port available. ![]() I suggest that you set up your UNIX/Linux environment before proceeding. If you are more a UNIX/Linux-type admin, it may be a good idea to create a UNIX/Linux only lab according to this howto – this will get you aquainted to the software. Please read through it, and understand how stunnel works before proceeding. I will use the settings from this tutorial while setting up the Windows side. Please note that the stock syslogd does NOT support connection oriented (TCP) syslog, so you need to replace it by something else if you would like to use stunnel.Īs I wrote, I try not to duplicate the UNIX/Linux side howto’s available. I selected this scenario because syslog-ng is quite common and chances are good that you will use it if you think about securely transfering Syslog data to UNIX/Linux. It supports raw TCP, only, so this is the mode of choice. Fortunately, Adiscon products support both raw TCP syslog as well as RFC 3195, so you can talk to whatever you have on the UNIX/Linux side.įor this article, I assume that you run syslog-ng on the UNIX/Linux side. Consequently, you need to use a Syslog implementation that supports TCP, either non-standard raw TCP or one of the newer standards like RFC 3195 (RFC 3195 supports encryption by itself, so it is best to check first if your application supports this – if it does, this is better than setting up a tunnel). As such, classical UDP-based syslog can not be used for tunneling. Tunneling, as done by stunnel, requires connection oriented communication. As such, it is vital that the portal and the respective program that is talking to it are on the same machine, otherwise data would travel partly unencrypted. The transfer to the portals is done via unencrypted communication. Stunnel, in turn, takes the data received from the client, encrypts it via ssl, sends it to the remote tunnel portal and that remote portal sends it to the recipient process on the remote machine. The non-ssl aware client and server software is configured to not directly talk to the remote partner, but to the local (s)tunnel portal instead. Both on the client and on the server machine, tunnel portals are created. The free stunnel project provides a way to use ssl communication for any non-ssl aware client and server (daemon). ![]() It is a mini-howto that primarily focusses on the Windows side because there are many good descriptions for the UNIX/Linux side. ![]() This article describes why and how this can be done. Windows Event Log data can securely be forwarded to a UNIX/Linux based syslogd via stunnel.
0 Comments
Leave a Reply. |