-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/06/15 18:09, Sebastian Rubenstein wrote: > Hi, > > I compiled and installed OpenVPN 2.3.7 on Debian 7 using > openvpn-2.3.7.zip downloaded from OpenVPN's official site. > > In a terminal, I launched openvpn using a config file and below is > a portion of the log: > > username@hostname:~$ sudo openvpn example.conf Fri Jun 12 OpenVPN > 2.3.7 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Jun 12 2015 > Fri Jun 12 library versions: OpenSSL 1.0.1e 11 Feb 2013, LZO 2.06 > > Question: Why does my manually compiled OpenVPN use OpenSSL > 1.0.1e? Is it due to the fact that when I was compiling OpenVPN, > the source code uses whatever version of OpenSSL is installed on my > Debian 7 OS?
Yes, that is correct. And when OpenSSL is getting updated on your Debian install, you generally do not need to recompile OpenVPN at all. Next time OpenVPN is restarted, it will use the latest updated OpenSSL. > For your info, on my Debian 7 64-bit OS, the version of OpenSSL is 1.0.1e-2+deb7u16. The '-2+deb7u16' part of the version number is not present inside the OpenSSL library, that's an external package reference unique to Debian only. That's why OpenVPN only sees '1.0.1e' - -- kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlV7HdEACgkQDC186MBRfrqvAACfWkW2GxZAWCxHwLIdtXQrTrco JoQAnijZC5zxFCDlMlw5vvEP3rBgijsi =mcL+ -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
