Changes between Version 32 and Version 33 of BuildingUsingGenericBuildsystem

Timestamp:

05/11/12 13:32:12 (12 years ago)

Author:

Samuli Seppänen

Comment:

--

BuildingUsingGenericBuildsystem

@@ -300 +300 @@
 The [http://sourceforge.net/projects/osslsigncode/ osslsigncode] tool is used to sign OpenVPN installer, executables and TAP-drivers. Official OpenVPN releases will be signed with  OpenVPN Technologies, Inc. code signing keys. However, it's fairly easy to build a custom version of OpenVPN and sign it with your own code-signing keys.
 
+== Installing osslsigncode ==
+
+The build system uses [http://sourceforge.net/projects/osslsigncode/ osslsigncode] to sign the produced libraries and executables. A recent version (1.4+) is required, although earlier versions can be used with minor modifications to the codesign() method in the scripts. More specifically, the assumption is that a pkcs12 keystore is used for signing, and osslsigncode 1.3 and earlier don't support pkcs12 yet.
+
+After [http://sourceforge.net/projects/osslsigncode/ fetching osslsigncode], make sure you have OpenSSL and Curl development libraries installed. The latter is used for timestamping support. Extract the osslsigncode tarball and issue the usual commands:
+
+{{{
+$ ./configure
+$ make
+$ sudo make install
+}}}
+
+This will put osslsigncode in PATH where the build system can find it.
+
 == Using verified certificates ==