I think you don't have to use dso at all. In my case, I don't use dso,
but if I remember well, I have to use the parameter "-engine
engine_name" when executing openssl. When using openssh, it works by
default. You have to make some minor modifications in openssh though.
My init is like:
void
EN
Yes it is possible to do it. You have to add the --static flag in the makefile
of the root dir of the openssl release that you are compiling. This flag must
be added both to CFLAGS for compiling and LDFLAGS for linking. For further
use, if you continue integration eg. with openssh, you will als
ok. I 'll check it a little bit tonight and send it you tomorrow.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manag
I have made such an engine and a driver some time ago. The approach
depends on the special details of your hardware.
In my case, I made a linux char driver that "talked" with the encryption
hardware, and an openssl-engine
that used this driver through the read/write system calls.
Additionally, I
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 th
Hi everybody.
I want to use a DES ECB/CBC encryption/decryption hardware with openssl.
I 've already built a linux driver that writes to and reads from the device,
and also provides device control, such as setting the keys, ecb or cbc mode,
initialization vector for cbc. The driver is tested and wo
