engine-corner / engine-chil Goto Github PK

Hi. I was wondering if this engine is compatible with OpenSSL 1.1.1?
I compiled it successfully using --with-openssl configuration option together with OpenSSL 1.1.1c.
However, the library files produced are in folder ../lib/engines instead of what i'd expect ../lib/engines-1.1/.
If i try to use them anyway i get segmentation fault then.

Hello,

We support an application that uses nCipher HSM and we are still using OpenSSL 1.0.2.
We are urged to upgrade to OpenSSL 1.1.1 and now we are facing issues because the CHIL engine is not supported anymore by OpenSSL.
We found out this repository and hoped that it will help us but unfortunately the port of the CHIL engine was not done for Windows platform :-/ (mainly due to libtool usage)
We are a little be lost in the replacement of the DSO API on Windows ...

By chance, do you have any Windows version of CHIL available ?

Thanks in advance

Absence of this macro file trips me up every time I check out a fresh copy. Should we bundle it into the repository? Its license seems benign enough.

e_chil.c has the current OpenSSL license, but should it? Considering OpenSSL itself is moving to an Apache license, I see no practical reason to stay with the old. Question is what to move to. My personal preferences are the Apache License or some form of BSD license, but I'd like to hear other opinions as well.

(in the mean time, I'll chase down those who have somehow tinkered with e_chil.c)

autoreconf -i outputs:
< lot of lines about libtoolize>

configure.ac:18: error: possibly undefined macro: AC_MSG_FAILURE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1

But if you drop the lines below from configure.ac the autoreconf -i;./configure;make sequence works:

AX_CHECK_OPENSSL(
  [have_openssl=yes],
  [AC_MSG_FAILURE([could not locate OpenSSL])]
)

Tested at Debian GNU/Linux 9 with OpenSSL 1.1.0j 20 Nov 2018.

With the current master branch cloned I get:

$ autoreconf -i
aclocal: warning: couldn't open directory 'm4': No such file or directory
configure.ac:18: error: possibly undefined macro: AC_MSG_FAILURE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1

Which seems to be addressed in #11

Perhaps this should be mentioned in the README?