Hi, In fact, we load our driver in the "zencod_init()" function using the ptr_zencod_board_status() fct call. This function performs a test (board status), and load the driver (if not loaded) through a small crypto API named zenbridge.
Fred -----Message d'origine----- De : Ioannis Liverezas [mailto:[EMAIL PROTECTED] Envoy� : mardi 29 juin 2004 15:45 � : Fr�d�ric Donnat; [EMAIL PROTECTED] Objet : RE : using DES hardware with openssl Thanx to all for your help. I 've studied the engine API and the zencod code and I began coding using zencod as an example. I 'm not sure if this is the way that things work, but if I 'm right, each time the engine needs for example to encrypt or decrypt a data buffer, it has to open and close the device (eg /dev/encdev). This is done by the zencod library, each time, eg for the case of cbc, the function ptr_zencod_xdes_cipher is called. Is this right or wrong? If it is correct, this will cause a performance loss. If so, how should the device be opened and closed for the best performance? If I am wrong, I was unable to find out where the engine opens or closes the device. Could you please tell me how and where this is done (in the case of zencod)? ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
