GÉANTLink

Suite of EAP supplicants for Windows - IEEE 802.1X plug-ins for enterprise network authentication

Building

Building Environment Requirements

• Microsoft Windows Vista or later
• Microsoft Visual Studio 2010 SP1
• msgfmt.exe from gettext; Hint: Poedit contains up-to-date binary Win32 compiled gettext-utilities. Install it and add GettextTools\bin folder to path.
• sed.exe and grep.exe
• MsiDb.Exe and other command line utilities for MSI packaging distributed as a part of Microsoft Windows SDK (installed with Visual Studio). Add SDK's Bin folder to path.

wxWidgets

GÉANTLink is using wxWidgets v3.0.2 static libraries. Unfortunately, dynamic libraries (DLL) variant is available as a binary download only. Therefore static libraries needs to be compiled from source.

Compiling wxWidgets Win32 static libraries

1. Start Visual Studio Command Prompt (2010)
2. Change working directory to build\msw
3. Run: nmake /f makefile.vc /ls RUNTIME_LIBS=static SHARED=0
4. Run: nmake /f makefile.vc /ls RUNTIME_LIBS=static SHARED=0 BUILD=release

Compiling wxWidgets x64 static libraries

1. Start Visual Studio x64 Cross Tools Command Prompt (2010)
2. Change working directory to build\msw
3. Run: nmake /f makefile.vc /ls RUNTIME_LIBS=static SHARED=0 TARGET_CPU=X64
4. Run: nmake /f makefile.vc /ls RUNTIME_LIBS=static SHARED=0 TARGET_CPU=X64 BUILD=release

Specifying wxWidgets path

GÉANTLink compilation references wxWidgets libraries using WXWIN environment variable. Please set it to wxWidgets folder (i.e. C:\SDK\wxWidgets\3.0.2).

Digital Signing of Build Outputs

In order to have the build process digitally sign output files, one should provide the following:

1. A signing certificate installed in the current user’s certificate store.
2. The following variables in the environment:

• ManifestCertificateThumbprint - set the value to certificate’s SHA1 thumbprint (hexadecimal, without spaces, i.e. bc0d8da45f9eeefcbe4e334e1fc262804df88d7e).
• ManifestTimestampUrl - set the value to URL used to perform timestamp signature (i.e. http://timestamp.verisign.com/scripts/timstamp.dll). In order to perform timestamp signing successfully, the computer running the build should be online and able to access this URL.

Please note that only Release builds are configured for timestamp signing. Debug configurations do not attempt to timestamp sign the resulting DLL and EXE files in order to speed up the building process and enable offline building.

Building

Building in Visual Studio IDE

GÉANTLink can be build and debugged opening VS10Solution.sln in Visual C++ 2010 IDE.

Before one can attempt to debug EAP DLLs, you should run nmake register from an elevated command prompt. See Building in command line chapter below.

Next, one must configure a network profile actually using GÉANTLink for the authentication.

GÉANTLink EAP modules are divided into two DLLs: backend (i.e. EAPTTLS.dll) and GUI (i.e. EAPTTLSUI.dll).

Backend DLL

The backend DLL is loaded by Eap3Host.exe process when connecting to the network. One approach to debug the module is to start Visual C++ elevated, open VS10Solution.sln, and attach to running Eap3Host.exe process. On initial connection attempt Eap3Host.exe will load the DLL and will not release it until EapHost service is restarted. To debug early life of our backend DLL, uncomment Sleep(10000) in DllMain() of the module, and set breakpoints. This should give you plenty of time to attach the debugger to Eap3Host.exe process before our DLL starts servicing authentication.

GUI DLL

The GUI DLL is loaded by DllHost.exe process on XML profile configuration import/export and when interactive user interface is required. A few seconds after desired function call has finished, DllHost.exe terminates and releases the DLL. To debug early life of our GUI DLL, uncomment Sleep(10000) in DllMain() of the module, and set breakpoints. This should give you plenty of time to attach the debugger to DllHost.exe process before our DLL starts.

Building in command line

Use of standard command prompt is recommended, providing that Microsoft Visual Studio 2010 folders containing nmake.exe and devenv.com are added to the path.

Use Microsoft NMAKE to build the project.

Command	Explanation
nmake Clean	Deletes all intermediate and output files.
nmake Register	Builds a debug version of project, registers DLLs, and adds Start Menu shortcuts. For testing and development purposes only! Requires elevated command prompt.
nmake Unregister	Removes Start Menu shortcuts, unregisters DLLs. For testing development purposes only! Requires elevated command prompt.
nmake Setup	Builds a release version of project and release MSI setup files. The resulting files can be found in output\Setup folder.
nmake SetupDebug	Builds a debug version of project and debug MSI setup files. The resulting files can be found in output\Setup folder.

The /ls flag can be appended to the commands above to reduce NMAKE’s verbosity. You can combine multiple targets (i.e. nmake Unregister Clean). Please, see NMAKE reference for further reading.