View source for Building and installing the eToken RPM

Unfortunately we are not allowed to post binary RPMs on this site publicly, as it includes a repackaged version of the Aladdin RTE software. For Nikhef, SARA and IGTF members a binary RPM is available in http://www.nikhef.nl/grid/ndpf/files/Aladdin-eToken/etoken-mkproxy/

====Building the etoken-mkproxy RPM====
If you use a <tt>~/.rpmmacros</tt> file you can build the RPM as a non-root user.  For example, with the following <tt>.rpmmacros</tt> file 
  %HOME                   %(echo "$HOME")
  %_topdir                %{HOME}/rpmbuild
  %_tmppath               %{_topdir}/tmp
and accompanying directory structure
  ~/rpmbuild/tmp
  ~/rpmbuild/SRPMS
  ~/rpmbuild/SOURCES
  ~/rpmbuild/BUILD
  ~/rpmbuild/SPECS
  ~/rpmbuild/RPMS/i386
you can build the <tt>etoken-proxy</tt> RPM in your home directory.

* First, Install the http://www.nikhef.nl/~janjust/etoken-mkproxy/etoken-mkproxy-LATEST.nosrc.rpm file
  rpm -i http://www.nikhef.nl/~janjust/etoken-mkproxy/etoken-mkproxy-LATEST.nosrc.rpm
* Unpack the .rar file using
  rar x eToken_PKI_Client_for_Linux_v3_65.rar
which will extract the files
* <tt>etoken-3-65.3-linux-Fedora-i386.tar.gz</tt> : Fedora Core 4 and higher
* <tt>etoken-3-65.3-linux-redhat-i386.tar.gz</tt> : Redhat Enterprise Linux 4 and higher
* <tt>etoken-3-65.3-linux-suse-i386.tar.gz</tt> : Novell Suse Linux
(and a few others) to the current directory.

Grab the <tt>.tar.gz</tt> tarball that closest matches your Linux distribution and place it in the <tt>SOURCES</tt> directory of your <tt>rpmbuild</tt> tree, e.g. with the directory structure from above
  ~/rpmbuild/SOURCES

Now build the RPM using
  rpmbuild -bb ~/rpmbuild/SPECS/etoken-mkproxy.spec
This will take quite some time, but eventually you should end up with a file
  ~/rpmbuild/RPMS/i386/etoken-mkproxy-''<VERSION>''.''<PLATFORM>''.i386.rpm
where ''<VERSION>'' is the latest and greatest version of the <tt>etoken-mkproxy</tt> RPM and ''<PLATFORM>'' is the platform type on which the RPM is built:
* 'rhel4' for CentOS 4 / Scientific Linux 4 / RedHat Enterprise Linux 4
* 'fc5' for Fedora Core 5
* 'suse10' for SuSE and openSuSE

====Installing the etoken-mkproxy RPM====
Installing the <tt>etoken-mkproxy</tt> RPM is quite simple but requires <tt>root</tt> access.
  rpm -i ~/rpmbuild/RPMS/i386/etoken-mkproxy-''<VERSION>''.''<PLATFORM>''.i386.rpm
where again, ''<VERSION>'' is the latest and greatest version of the <tt>etoken-mkproxy</tt> RPM and ''<PLATFORM>'' is the platform type on which the RPM is built:
* 'rhel4' for CentOS 4 / Scientific Linux 4 / RedHat Enterprise Linux 4
* 'fc5' for Fedora Core 5
* 'suse10' for SuSE and openSuSE

For Nikhef, SARA and IGTF members the following will also work:
  # FC5:
  rpm -ivh http://www.nikhef.nl/grid/ndpf/files/Aladdin-eToken/etoken-mkproxy/etoken-mkproxy-LATEST.fc5.i386.rpm
  # RHEL4:
  rpm -ivh http://www.nikhef.nl/grid/ndpf/files/Aladdin-eToken/etoken-mkproxy/etoken-mkproxy-LATEST.rhel4.i386.rpm
  # Suse10:
  rpm -ivh http://www.nikhef.nl/grid/ndpf/files/Aladdin-eToken/etoken-mkproxy/etoken-mkproxy-LATEST.suse10.i386.rpm

The RPM will install the necessary startup scripts in <tt>/etc/init.d</tt>, after which it will start the eToken daemons <tt>etokend</tt> and <tt>etsrvd</tt>.

'''NOTES'''
* there is only a ''i386'' version of the <tt>etoken-mkproxy</tt> RPM. This is because the Aladdin RTE software is available only for 32-bit platforms. This RPM will install correctly on x86_64 architectures as well, however.
* the pcscd daemon is used only if no <tt>/etc/init.d/pcscd</tt> file is detected during RPM installation.
* some binaries have hard-coded RPATHs to enable their correct functioning when the <tt>LD_LIBRRARY_PATH</tt> environment variable is not set.

'''Congratulations!''' 
You are now ready to use your Aladdin eToken PRO on Linux!