pkcs11_startup was still looking for an old library filename in
order to determine if the CCA 4+ library is really installed or not.
This was preventing the CCA token from being properly configured in
opencryptoki 2.3 and later.
Signed-off-by: Klaus Heinrich Kiwi <[email protected]>
---
usr/sbin/pkcs11_startup/pkcs11_startup.in | 9 +++++----
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/usr/sbin/pkcs11_startup/pkcs11_startup.in
b/usr/sbin/pkcs11_startup/pkcs11_startup.in
index 66d574e..6bdeaa7 100644
--- a/usr/sbin/pkcs11_startup/pkcs11_startup.in
+++ b/usr/sbin/pkcs11_startup/pkcs11_startup.in
@@ -424,10 +424,11 @@ fi
# add the CCA token
# CCA stdll is always built by default in supported archs, so check for both
-# the CCA stdll *and* for a library needed by the CCA token - KlausK Jul'09
-# The libraries required by CCA token are provided by the 'xcryptolinzGA'
-# RPM package, available from the IBM web site.
-if [ -f @libdir@/opencryptoki/stdll/libpkcs11_cca.so ] && [ -f
/usr/lib64/libcsulmkapi.so.1 ]
+# the CCA stdll *and* for a library needed by the CCA token.
+# For opencryptoki 2.3 and up, we *require* CCA 4.0 or later, which can be
+# obtained from the IBM website
+# http://www.ibm.com/security/cryptocards/pciecc/ordersoftware.shtml
+if [ -f @libdir@/opencryptoki/stdll/libpkcs11_cca.so ] && [ -f
/usr/lib64/libcsulcca.so ]
then
@sbindir@/pkcs_slot 0 cca
fi
--
1.7.2.2
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Opencryptoki-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
