Voltage Identity-Based Encryption (IBE) Toolkit Install Guide

Windows Binaries

The Windows Binaries package contains pre-built static libraries and header files. To use the Toolkit, simply #include "vibe.h" in your source and link against vibe.lib, vibecrypto.lib, and vibeproviders.lib.

If you use either the Windows default storage provider or the Windows default transport provider, your application will also need to link against crypt32.lib and wininet.lib. Make sure you have these libraries from the latest version of the Windows Platform SDK, which you can download from:

http://www.microsoft.com/msdownload/platformsdk/sdkupdate/

Click on 'Core SDK' under 'Windows Server 2003 SDK' to download the necessary headers and libraries. Make sure to point your Visual Studio development environment at the new SDK libraries by going to Tools->Options...->Directories (in most cases, the SDK should be first in your search path).

Note that due to incompatiblities with Visual C++ 6.0, you should not install the Windows XP SP2 SDK.

Windows Source

The Windows Source package includes everything you need to build the Toolkit from scratch. The lib/win32/ directory contains Visual Studio 6 projects for building the three main Toolkit libraries: vibe.lib, vibecrypto.lib, and vibeproviders.lib. You can then link against these three libraries to build a Toolkit-enabled application.

You will need the latest version of the Windows Platform SDK to build the Toolkit. You can download the Platform SDK from:

http://www.microsoft.com/msdownload/platformsdk/sdkupdate/

Click on 'Core SDK' under 'Windows Server 2003 SDK' to download the necessary headers and libraries. Make sure to point your Visual Studio development environment at the new SDK libraries and headers by going to Tools-> Options...-> Directories (in most cases, the SDK should be first in your search path).

Note that due to incompatiblities with Visual C++ 6.0, you should not install the Windows XP SP2 SDK.

Both of the Windows packages include a Token Handler application, which is used for browser-based authentication. To install the Token Handler, run install.bat in the tokenhandler/ directory. The script installs a set of registry entries that allow the Token Handler application to process token data downloaded through a browser. To uninstall the Token Handler, just run uninstall.bat.

For more information about browser-based authentication and how it works, click here.

Reference Server – Binaries

The binaries package contains a pre-built version of the Reference Server.

To use the Reference Server transport provider (the "LocalTest"
provider), simply #include "localtest.h" in your source and link against
vibelocaltest.lib and vibeserver.lib.

Reference Server – Source

The Reference Server source should be unpacked next to the main Toolkit source. Then, build the two Visual Studio 6 projects (vibeserver and vibelocaltest) in lib/win32/.

To use the Reference Server transport provider (the "LocalTest"
provider), simply #include "localtest.h" in your source and link against
vibelocaltest.lib and vibeserver.lib.

Back to top

RPM Distribution

The RPM contains binary libraries as well as all the include files that are needed to access the libraries. The RPMs are built for RedHeat Enterprise Linux 4, but should work on most similar recent versions of Linux. If you want to develop applications that use the Toolkit, the RPM distribution is the recommended install.

Source Distribution

The Linux source distribution uses the autoconf tools for maximum portability. However, in most cases, building the Toolkit will not require these tools to be present.

The Linux Source package includes everything you need to build the Toolkit from scratch, except for OpenSSL (version 0.9.7c or later), which must be available on your path (the Toolkit links against libcrypto.a). Most recent Linux distributions will have a working version of OpenSSL already installed.

The lib/unix directory contains a configure file that builds the Makefiles that then build all libraries which are needed to build a Toolkit-enabled application. So, to build the Toolkit, all you need to do is:

./configure
make

Both static and dynamic libraries will be built in the lib/.libs directory. To install them type:

make install

For special build options (e.g., debug builds, different install directory), flags can be passed to configure. For example:

./configure CFLAGS=-O2 --libdir /usr/shared/lib

will build the libraries with the flag –O2 passed to the compiler and set the library install path to /usr/shared/lib.

The distribution also includes the autoconf source files. If you have the autoconf tools installed, you can rebuild them using aclocal, autoconf, automake and libtool. Refer to the autoconf documnetation for details of how to do this.

Compatibility

The Toolkit is tested to work on Linux (RedHat x86 versions) only; however it should compile and run on other mainstream distributions. There is one library that is not shipped in source form, libictk.a. The precompiled version that ships with the Toolkit was compiled with -mcpu=i686.

If this versions of libictk.does not work for you or you need a different Intel or non-Intel CPU type supported, please contact us.

Using the Toolkit

To use the Toolkit, simply #include "vibe.h" in your source and link against the static libraries. For most applications, you will need to link against libvibe.a, libvibecrypto.a, and libvibeproviders.a.

If you use the default Unix transport provider, your application will also need to link against libcurl. Most distributions ship with libcurl; if you don’t have it installed, you can download it from:

http://curl.haxx.se/download.html

Make sure that libcurl is in your path.

Sample Programs

The Toolkit distribution contains some sample programs, located in the sample/ directory. After building the Toolkit, just type make, and the sample programs will be built.

Reference Server

The Reference Server should be unpacked next to the main Toolkit source.
To compile it, all you need to do is:

./configure
make

The main Toolkit makefile will detect the presence of the server files and build the server.

To use the Reference Server transport provider (the "LocalTest"
provider), simply #include "localtest.h" in your source and link against
the static libraries libvibelocaltest.a and libvibeserver.a.

Back to top