Commit e9d09751 authored by Francis Dupont's avatar Francis Dupont
Browse files

AEP keyper PKCS#11 provider is available in 64 bits

parent f163503b
......@@ -236,18 +236,12 @@ $ <userinput>patch -p1 -d openssl-0.9.8zc \
$ <userinput>cp /opt/pkcs11/usr/lib/</userinput>
This library is only available for Linux as a 32-bit
binary. If we are compiling on a 64-bit Linux system, it is
necessary to force a 32-bit build, by specifying -m32 in the
build options.
Finally, the Keyper library requires threads, so we
The Keyper library requires threads, so we
must specify -pthread.
$ <userinput>cd openssl-0.9.8zc</userinput>
$ <userinput>./Configure linux-generic32 -m32 -pthread \
$ <userinput>./Configure linux-x86_64 -pthread \
--pk11-libname=/opt/pkcs11/usr/lib/ \
--pk11-flavor=sign-only \
......@@ -370,15 +364,9 @@ $ <userinput>./Configure linux-x86_64 -pthread \
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
The PKCS#11 library for the AEP Keyper is currently
only available as a 32-bit binary. If we are building on a
64-bit host, we must force a 32-bit build by adding "-m32" to
the CC options on the "configure" command line.
$ <userinput>cd ../bind9</userinput>
$ <userinput>./configure CC="gcc -m32" --enable-threads \
$ <userinput>./configure --enable-threads \
--with-openssl=/opt/pkcs11/usr \
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment