wbrawner/openssl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
openssl/crypto/engine/Makefile.ssl

210 lines
10 KiB
Text
Raw Normal View History

Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
#
# OpenSSL/crypto/engine/Makefile
#
DIR= engine
TOP= ../..
CC= cc
INCLUDES= -I.. -I../../include
CFLAG=-g
INSTALL_PREFIX=
OPENSSLDIR= /usr/local/ssl
INSTALLTOP=/usr/local/ssl
MAKE= make -f Makefile.ssl
MAKEDEPEND= $(TOP)/util/domd $(TOP)
MAKEFILE= Makefile.ssl
AR= ar r
CFLAGS= $(INCLUDES) $(CFLAG)
GENERAL=Makefile
TEST= enginetest.c
APPS=
LIB=$(TOP)/libcrypto.a
LIBSRC= engine_err.c engine_lib.c engine_list.c engine_openssl.c \
This adds Atalla support code to the ENGINE framework. If you have an Atalla card, you should be able to compile with the "hw-atalla" switch with "./config" or "perl Configure", and then you can use the command- line switch "-engine atalla" inside speed, s_cient and s_server (after checking out note (1)). Notes: (1) I've turned on native name translation when loading the shared- library, but this means that the Unix shared library needs to be libatasi.so rather than atasi.so. I got around this in my testing by creating a symbollic link from /usr/lib/libatasi.so to the real library, but something better will be needed. It also assumes in win32 that the DLL will be called atasi.dll - but as I don't have a win32/atalla environment to try I have no idea yet if this is the case. (2) Currently DSA verifies are not accelerated because I haven't yet got a mod_exp-based variant of BN_mod_exp2_mont() that yields correct results. (3) Currently the "init()" doesn't fail if the shared library can load successfully but the card is not operational. In this case, the ENGINE_init() call will succeed, but all RSA, DSA, DH, and the two BN_*** operations will fail until the ENGINE is switched back to something that does work. I expect to correct this next. (4) Although the API for the Atalla card just has the one crypto function suggesting an RSA private key operation - this is in fact just a straight mod_exp function that ignores all the RSA key parameters except the (private) exponent and modulus. This is why the only accelerator work is taking place inside the mod_exp function and there's no optimisation of RSA private key operations based on CRT etc.
2000-06-14 17:04:10 +00:00
hw_atalla.c hw_cswift.c hw_ncipher.c
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
LIBOBJ= engine_err.o engine_lib.o engine_list.o engine_openssl.o \
This adds Atalla support code to the ENGINE framework. If you have an Atalla card, you should be able to compile with the "hw-atalla" switch with "./config" or "perl Configure", and then you can use the command- line switch "-engine atalla" inside speed, s_cient and s_server (after checking out note (1)). Notes: (1) I've turned on native name translation when loading the shared- library, but this means that the Unix shared library needs to be libatasi.so rather than atasi.so. I got around this in my testing by creating a symbollic link from /usr/lib/libatasi.so to the real library, but something better will be needed. It also assumes in win32 that the DLL will be called atasi.dll - but as I don't have a win32/atalla environment to try I have no idea yet if this is the case. (2) Currently DSA verifies are not accelerated because I haven't yet got a mod_exp-based variant of BN_mod_exp2_mont() that yields correct results. (3) Currently the "init()" doesn't fail if the shared library can load successfully but the card is not operational. In this case, the ENGINE_init() call will succeed, but all RSA, DSA, DH, and the two BN_*** operations will fail until the ENGINE is switched back to something that does work. I expect to correct this next. (4) Although the API for the Atalla card just has the one crypto function suggesting an RSA private key operation - this is in fact just a straight mod_exp function that ignores all the RSA key parameters except the (private) exponent and modulus. This is why the only accelerator work is taking place inside the mod_exp function and there's no optimisation of RSA private key operations based on CRT etc.
2000-06-14 17:04:10 +00:00
hw_atalla.o hw_cswift.o hw_ncipher.o
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
SRC= $(LIBSRC)
EXHEADER= engine.h
HEADER= $(EXHEADER)
ALL= $(GENERAL) $(SRC) $(HEADER)
top:
(cd ../..; $(MAKE) DIRS=crypto SDIRS=$(DIR) sub_all)
all: lib
lib: $(LIBOBJ)
$(AR) $(LIB) $(LIBOBJ)
$(RANLIB) $(LIB)
@touch lib
files:
$(PERL) $(TOP)/util/files.pl Makefile.ssl >> $(TOP)/MINFO
links:
@$(TOP)/util/point.sh Makefile.ssl Makefile
@$(PERL) $(TOP)/util/mklink.pl ../../include/openssl $(EXHEADER)
@$(PERL) $(TOP)/util/mklink.pl ../../test $(TEST)
@$(PERL) $(TOP)/util/mklink.pl ../../apps $(APPS)
install:
@for i in $(EXHEADER) ; \
do \
(cp $$i $(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl/$$i; \
chmod 644 $(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl/$$i ); \
done;
tags:
ctags $(SRC)
tests:
lint:
lint -DLINT $(INCLUDES) $(SRC)>fluff
depend:
$(MAKEDEPEND) $(INCLUDES) $(DEPFLAG) $(PROGS) $(LIBSRC)
dclean:
$(PERL) -pe 'if (/^# DO NOT DELETE THIS LINE/) {print; exit(0);}' $(MAKEFILE) >Makefile.new
mv -f Makefile.new $(MAKEFILE)
clean:
rm -f *.o */*.o *.obj lib tags core .pure .nfs* *.old *.bak fluff
# DO NOT DELETE THIS LINE -- make depend depends on it.
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_err.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
engine_err.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
engine_err.o: ../../include/openssl/cast.h ../../include/openssl/crypto.h
engine_err.o: ../../include/openssl/des.h ../../include/openssl/dh.h
engine_err.o: ../../include/openssl/dsa.h ../../include/openssl/e_os2.h
engine_err.o: ../../include/openssl/engine.h ../../include/openssl/err.h
engine_err.o: ../../include/openssl/evp.h ../../include/openssl/idea.h
engine_err.o: ../../include/openssl/lhash.h ../../include/openssl/md2.h
engine_err.o: ../../include/openssl/md5.h ../../include/openssl/mdc2.h
engine_err.o: ../../include/openssl/objects.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_err.o: ../../include/openssl/opensslconf.h
engine_err.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_err.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
engine_err.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_err.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_err.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
engine_lib.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
engine_lib.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
engine_lib.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
engine_lib.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_lib.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
engine_lib.o: ../../include/openssl/e_os.h ../../include/openssl/e_os2.h
engine_lib.o: ../../include/openssl/engine.h ../../include/openssl/err.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_lib.o: ../../include/openssl/evp.h ../../include/openssl/idea.h
engine_lib.o: ../../include/openssl/lhash.h ../../include/openssl/md2.h
engine_lib.o: ../../include/openssl/md5.h ../../include/openssl/mdc2.h
engine_lib.o: ../../include/openssl/objects.h
engine_lib.o: ../../include/openssl/opensslconf.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_lib.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_lib.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
engine_lib.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_lib.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_lib.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
engine_lib.o: ../cryptlib.h engine_int.h
engine_list.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
engine_list.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
engine_list.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
engine_list.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_list.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
engine_list.o: ../../include/openssl/e_os.h ../../include/openssl/e_os2.h
engine_list.o: ../../include/openssl/engine.h ../../include/openssl/err.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_list.o: ../../include/openssl/evp.h ../../include/openssl/idea.h
engine_list.o: ../../include/openssl/lhash.h ../../include/openssl/md2.h
engine_list.o: ../../include/openssl/md5.h ../../include/openssl/mdc2.h
engine_list.o: ../../include/openssl/objects.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_list.o: ../../include/openssl/opensslconf.h
engine_list.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_list.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
engine_list.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_list.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_list.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
engine_list.o: ../cryptlib.h engine_int.h
engine_openssl.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
engine_openssl.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
engine_openssl.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
engine_openssl.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_openssl.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
engine_openssl.o: ../../include/openssl/dso.h ../../include/openssl/e_os.h
engine_openssl.o: ../../include/openssl/e_os2.h ../../include/openssl/engine.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_openssl.o: ../../include/openssl/err.h ../../include/openssl/evp.h
engine_openssl.o: ../../include/openssl/idea.h ../../include/openssl/lhash.h
engine_openssl.o: ../../include/openssl/md2.h ../../include/openssl/md5.h
engine_openssl.o: ../../include/openssl/mdc2.h ../../include/openssl/objects.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_openssl.o: ../../include/openssl/opensslconf.h
engine_openssl.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_openssl.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
engine_openssl.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
engine_openssl.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
engine_openssl.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
engine_openssl.o: ../cryptlib.h engine_int.h
hw_atalla.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
hw_atalla.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
hw_atalla.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
hw_atalla.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
This adds Atalla support code to the ENGINE framework. If you have an Atalla card, you should be able to compile with the "hw-atalla" switch with "./config" or "perl Configure", and then you can use the command- line switch "-engine atalla" inside speed, s_cient and s_server (after checking out note (1)). Notes: (1) I've turned on native name translation when loading the shared- library, but this means that the Unix shared library needs to be libatasi.so rather than atasi.so. I got around this in my testing by creating a symbollic link from /usr/lib/libatasi.so to the real library, but something better will be needed. It also assumes in win32 that the DLL will be called atasi.dll - but as I don't have a win32/atalla environment to try I have no idea yet if this is the case. (2) Currently DSA verifies are not accelerated because I haven't yet got a mod_exp-based variant of BN_mod_exp2_mont() that yields correct results. (3) Currently the "init()" doesn't fail if the shared library can load successfully but the card is not operational. In this case, the ENGINE_init() call will succeed, but all RSA, DSA, DH, and the two BN_*** operations will fail until the ENGINE is switched back to something that does work. I expect to correct this next. (4) Although the API for the Atalla card just has the one crypto function suggesting an RSA private key operation - this is in fact just a straight mod_exp function that ignores all the RSA key parameters except the (private) exponent and modulus. This is why the only accelerator work is taking place inside the mod_exp function and there's no optimisation of RSA private key operations based on CRT etc.
2000-06-14 17:04:10 +00:00
hw_atalla.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
hw_atalla.o: ../../include/openssl/dso.h ../../include/openssl/e_os.h
hw_atalla.o: ../../include/openssl/e_os2.h ../../include/openssl/engine.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_atalla.o: ../../include/openssl/err.h ../../include/openssl/evp.h
hw_atalla.o: ../../include/openssl/idea.h ../../include/openssl/lhash.h
hw_atalla.o: ../../include/openssl/md2.h ../../include/openssl/md5.h
hw_atalla.o: ../../include/openssl/mdc2.h ../../include/openssl/objects.h
This adds Atalla support code to the ENGINE framework. If you have an Atalla card, you should be able to compile with the "hw-atalla" switch with "./config" or "perl Configure", and then you can use the command- line switch "-engine atalla" inside speed, s_cient and s_server (after checking out note (1)). Notes: (1) I've turned on native name translation when loading the shared- library, but this means that the Unix shared library needs to be libatasi.so rather than atasi.so. I got around this in my testing by creating a symbollic link from /usr/lib/libatasi.so to the real library, but something better will be needed. It also assumes in win32 that the DLL will be called atasi.dll - but as I don't have a win32/atalla environment to try I have no idea yet if this is the case. (2) Currently DSA verifies are not accelerated because I haven't yet got a mod_exp-based variant of BN_mod_exp2_mont() that yields correct results. (3) Currently the "init()" doesn't fail if the shared library can load successfully but the card is not operational. In this case, the ENGINE_init() call will succeed, but all RSA, DSA, DH, and the two BN_*** operations will fail until the ENGINE is switched back to something that does work. I expect to correct this next. (4) Although the API for the Atalla card just has the one crypto function suggesting an RSA private key operation - this is in fact just a straight mod_exp function that ignores all the RSA key parameters except the (private) exponent and modulus. This is why the only accelerator work is taking place inside the mod_exp function and there's no optimisation of RSA private key operations based on CRT etc.
2000-06-14 17:04:10 +00:00
hw_atalla.o: ../../include/openssl/opensslconf.h
hw_atalla.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_atalla.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
hw_atalla.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
This adds Atalla support code to the ENGINE framework. If you have an Atalla card, you should be able to compile with the "hw-atalla" switch with "./config" or "perl Configure", and then you can use the command- line switch "-engine atalla" inside speed, s_cient and s_server (after checking out note (1)). Notes: (1) I've turned on native name translation when loading the shared- library, but this means that the Unix shared library needs to be libatasi.so rather than atasi.so. I got around this in my testing by creating a symbollic link from /usr/lib/libatasi.so to the real library, but something better will be needed. It also assumes in win32 that the DLL will be called atasi.dll - but as I don't have a win32/atalla environment to try I have no idea yet if this is the case. (2) Currently DSA verifies are not accelerated because I haven't yet got a mod_exp-based variant of BN_mod_exp2_mont() that yields correct results. (3) Currently the "init()" doesn't fail if the shared library can load successfully but the card is not operational. In this case, the ENGINE_init() call will succeed, but all RSA, DSA, DH, and the two BN_*** operations will fail until the ENGINE is switched back to something that does work. I expect to correct this next. (4) Although the API for the Atalla card just has the one crypto function suggesting an RSA private key operation - this is in fact just a straight mod_exp function that ignores all the RSA key parameters except the (private) exponent and modulus. This is why the only accelerator work is taking place inside the mod_exp function and there's no optimisation of RSA private key operations based on CRT etc.
2000-06-14 17:04:10 +00:00
hw_atalla.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_atalla.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
hw_atalla.o: ../cryptlib.h engine_int.h vendor_defns/atalla.h
hw_cswift.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
hw_cswift.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
hw_cswift.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
hw_cswift.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
hw_cswift.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
hw_cswift.o: ../../include/openssl/dso.h ../../include/openssl/e_os.h
hw_cswift.o: ../../include/openssl/e_os2.h ../../include/openssl/engine.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_cswift.o: ../../include/openssl/err.h ../../include/openssl/evp.h
hw_cswift.o: ../../include/openssl/idea.h ../../include/openssl/lhash.h
hw_cswift.o: ../../include/openssl/md2.h ../../include/openssl/md5.h
hw_cswift.o: ../../include/openssl/mdc2.h ../../include/openssl/objects.h
- merged in the latest from the main trunk, fixed all conflicts - implemented nCipher support via the nfhwcrhk library (not well tested). - make update + make depend
2000-06-13 16:21:06 +00:00
hw_cswift.o: ../../include/openssl/opensslconf.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
hw_cswift.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_cswift.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
hw_cswift.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
Add code and changes to implement the ENGINE mechanism. These are the patches that Geoff had in a patch file in his play directory. NOTE for openssl-cvs: THIS IS A CVS BRANCH (BRANCH_engine). IT IS NOT FOR THE FAINTHEARTED TO PLAY WITH. The code works as it is, but it's not at all sure it ends up in the OpenSSL distributio in this form, so do not get dependent on it! Those rsyncing the repository are considered warned!
2000-05-25 19:55:54 +00:00
hw_cswift.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_cswift.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
hw_cswift.o: ../cryptlib.h engine_int.h vendor_defns/cswift.h
hw_ncipher.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
hw_ncipher.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
hw_ncipher.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
hw_ncipher.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
- merged in the latest from the main trunk, fixed all conflicts - implemented nCipher support via the nfhwcrhk library (not well tested). - make update + make depend
2000-06-13 16:21:06 +00:00
hw_ncipher.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
hw_ncipher.o: ../../include/openssl/dso.h ../../include/openssl/e_os.h
hw_ncipher.o: ../../include/openssl/e_os2.h ../../include/openssl/engine.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_ncipher.o: ../../include/openssl/err.h ../../include/openssl/evp.h
hw_ncipher.o: ../../include/openssl/idea.h ../../include/openssl/lhash.h
hw_ncipher.o: ../../include/openssl/md2.h ../../include/openssl/md5.h
hw_ncipher.o: ../../include/openssl/mdc2.h ../../include/openssl/objects.h
- merged in the latest from the main trunk, fixed all conflicts - implemented nCipher support via the nfhwcrhk library (not well tested). - make update + make depend
2000-06-13 16:21:06 +00:00
hw_ncipher.o: ../../include/openssl/opensslconf.h
Add the possibility to load prvate and public keys from an engine and implement it for nCipher hardware. The interface in itself should be clear enough, but the nCipher implementation is currently not the best when it comes to getting a passphrase from the user. However, getting it better is a little hard until a better user interaction method is create. Also, use the possibility in req, so we can start to create CSR's with keys from the nForce box. WARNING: I've made *no* tests yet, mostly because I didn't implement this on the machine where I have an nForce box to play with. All I know is that it compiles cleanly on Linux...
2000-07-06 18:40:10 +00:00
hw_ncipher.o: ../../include/openssl/opensslv.h ../../include/openssl/pem.h
hw_ncipher.o: ../../include/openssl/pem2.h ../../include/openssl/pkcs7.h
hw_ncipher.o: ../../include/openssl/rand.h ../../include/openssl/rc2.h
hw_ncipher.o: ../../include/openssl/rc4.h ../../include/openssl/rc5.h
hw_ncipher.o: ../../include/openssl/ripemd.h ../../include/openssl/rsa.h
hw_ncipher.o: ../../include/openssl/safestack.h ../../include/openssl/sha.h
hw_ncipher.o: ../../include/openssl/stack.h ../../include/openssl/x509.h
hw_ncipher.o: ../../include/openssl/x509_vfy.h ../cryptlib.h engine_int.h
`make update'
2000-06-29 21:26:46 +00:00
hw_ncipher.o: vendor_defns/hwcryptohook.h
Reference in a new issue Copy permalink