openCryptoki-2.1.5-6
所属分类:CA认证
开发工具:LINUX
文件大小:1142KB
下载次数:108
上传日期:2004-06-15 14:24:27
上 传 者:
管理员
说明: IBM的Linux上的PKCS#11实现
(IBM s Linux on the PKCS# 11 to achieve)
文件列表:
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\COPYRIGHTS (1776, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\AUTHORS (403, 2003-05-06)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\COPYING (15494, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\ChangeLog (0, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\FAQ (2439, 2004-01-09)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\INSTALL (6917, 2002-11-13)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\LICENSE (15494, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\Makefile.am (548, 2004-02-11)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\NEWS (0, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\TODO (328, 2004-01-09)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\bootstrap.sh (57, 2003-12-16)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\configure.in (6800, 2004-03-04)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\install-sh (5598, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\ltconfig (97712, 2002-08-23)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\ltmain.sh (138394, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\missing (6283, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\mkinstalldirs (727, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\doc\openCryptoki-HOWTO.pdf (85657, 2003-12-16)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\doc (0, 2004-06-15)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\rpm\openCryptoki.spec (6463, 2004-03-10)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\rpm (0, 2004-06-15)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\Makefile (512, 2003-05-06)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\des3_func.c (44490, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\des_func.c (56182, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\dh_func.c (24538, 2003-05-20)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\digest_func.c (99855, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\driver.c (15284, 2003-06-20)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\dsa_func.c (5470, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\md5.c (11466, 2003-08-27)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\md5.h (2995, 2003-08-27)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\misc_func.c (25748, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\obj_mgmt.c (37420, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\rsa_func.c (50610, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\sess_mgmt.c (30951, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver\ssl3_func.c (12865, 2002-08-02)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\driver (0, 2004-06-15)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\include\regress.h (1538, 2003-06-20)
openCryptoki-2.1.5-6\openCryptoki-2.1.5-6\testcases\include\rsadump.h (48845, 2002-08-02)
... ...
-- openCryptoki README -- Kent Yoder
REQUIREMENTS:
As of version 2.1, openCryptoki's soft token will require openssl-0.9.7.
This is as a result of moving to version 2.11 of the PKCS#11 specification,
which includes the AES algorithm. Since no hardware tokens yet support AES,
there is an option to intentionally not build the software token, which is
meant to be used for testing only. So your options are to either install
openssl-0.9.7 and build as normal, or use openssl-0.9.6, and run
'./configure --disable-swtok'.
Warning: Having both openssl 0.9.6 and 0.9.7 installed at the same time
can be tricky and most likely will only be detected at run time by a
segmentation fault (for instance if you link to libcrypto 0.9.7 and use
the header file from 0.9.6 to compile.) To be sure you get the soft
token compiled correctly I suggest doing
# mv /usr/include/openssl /usr/include/openssl.0.9.6
(make and install openssl-0.9.7 into the default location /usr/local/ssl)
# cd openCryptoki
# sh ./bootstrap.sh
# LDFLAGS=-L/usr/local/ssl/lib CFLAGS=-I/usr/local/ssl/include ./configure
# mv /usr/include/openssl.0.9.6 /usr/include/openssl
BUILD PROCESS:
First, run `sh bootstrap.sh`. This will create a configure script. Then the
standard:
$ ./configure
$ make
$ su -c 'make install'
If your stdll headers and libraries are not under any standard path, you'll
need to pass the paths to your files to the configure script. ie:
$ CPPFLAGS="-L/path/lib" LDFLAGS="-I/path/include" ./configure
See ./configure --help for info on various options. The default
behavior is to build any token whose libraries are found. You may
disable building any token with its corresponding --disable-
configure option.
RUNNING openCryptoki:
See http://www-124.ibm.com/developerworks/oss/opencryptoki/howto/index.html
or the docs section of
http://www-124.ibm.com/developerworks/projects/openCryptoki
ARCHITECTURE:
On any 32bit arch, openCryptoki is compiled using gcc and all the necessary
components are installed as 32bit executables/libraries as follows:
/usr/lib/pkcs11/PKCS11_API.so 32bit shared library
/usr/lib/pkcs11/stdll directory
/usr/lib/pkcs11/stdll/PKCS11_ICA.so 32bit shared library
/usr/lib/pkcs11/methods directory
/usr/lib/pkcs11/methods/pkcsconf 32bit executable
/usr/lib/pkcs11/methods/pkcs_slot Shell script
/usr/lib/pkcs11/methods/pkcs11_startup Shell script
/usr/sbin/pkcsslotd 32bit executable
On ***bit s390x, a ***bit gcc is used to compile the only 2 ***bit objects
used in openCryptoki:
/usr/lib/pkcs11/PKCS11_API.so*** ***bit shared library
/usr/lib/pkcs11/stdll/PKCS11_ICA.so*** ***bit shared library
On ppc***, the ***bit cross compiler is used to compile these 2 objects. On
both s390x and ppc***, the 32bit libraries and executables are installed as
well as the ***bit objects in order to have an environment where both 32bit
and ***bit PKCS#11 apps can run. On ppc and s390, pkcsslotd is compiled with
the -DPKCS*** flag, which makes all structures match their size on a ***bit
platform when being compiled 32bit. In this way, pkcsslotd can interact
with both 32 and ***bit executable/libraries.
近期下载者:
相关文件:
收藏者: