Compiled OpenVPN doesn't show pkcs in the log

[elpin]

Hey guys,

I've just successfully compiled an OpenVPN build 2.2.2 on my computer using the tutorial here: http://community.openvpn.net/openvpn/wi ... gOnWindows and I have to say it is brilliant. I have very little programming knowledge but was able to compile all the dependencies and the main OpenVPN build without a major problem. Thanks a lot to the author of the tutorial!

Now, my question, something I noticed when I run the newly compiled build is that the first line of the log says:

Code: Select all

Sat Jan 04 21:40:06 2014 OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] built on Jan  4 2014

But when I use the OpenVPN exe file provided by the official installer it says:

Code: Select all

Sat Jan 04 21:41:33 2014 OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Dec 15 2011

The PKCS11 "tag" is missing from my build. Now since I swim like a fish in the barrel when comes to all the SSLs and LZO2s, I'm not sure if the absence of that "tag" is important. What does PKCS11 actually do? I read it that it enumerates available token certificates, among other things. Does it mean my build can't properly read certificate files? If so, how do I get it in my build?

I used build_all python script to build OpenVPN and there were no errors or warnings during the compilation.

I'd be happy if you can clear things for me a bit. Thanks!

[elpin]

So, seems like I solved the problem. In case anybody stumbles upon the same problem, here's what I did:

I went to Settings.in file and modified the settings as following:

from

Code: Select all

# Uncomment to use the PKCS#11 helper library
!define USE_PKCS11 0
;!define INCLUDE_PKCS11

to

Code: Select all

# Uncomment to use the PKCS#11 helper library
!define USE_PKCS11 1
!define INCLUDE_PKCS11

Now the reason why I'm compiling my own OpenVPN build is because of an obfuscation patch made by Siren1117. I have the same problem enabling his patch as I had with PKCS though. I tried to put !define USE_OBFUSCATION in the Settings.in file but it wouldn't work