Hi, On Thu, May 28, 2020 at 03:59:20PM -0700, James Bottomley wrote: > Testing engines is problematic, so one of the prerequisites built for > the tests is a simple openssl engine that reads a non-standard PEM > guarded key. The test is simply can we run a client/server > configuration with the usual sample key replaced by an engine key. > The trivial engine prints out some operations and we check for these > in the log to make sure the engine was used to load the key and that > it correctly got the password. > > Signed-off-by: James Bottomley <james.bottom...@hansenpartnership.com> > > --- > v5: do not hard code dynamic library extension into openssl.cnf (MacOS) > v4: add OPENSSL_config(NULL) so debian checks will work > v3: added this patch > ---
So, how can we continue with this one? The engine key code is in, the
unit test code not.
Arne, James, can we converge on something here?
I would like something "as simple as possible", aka "little configure magic"
- if that means "MacOS engine is built and loaded as .so and not .dynlib,
but the test passes" I would prefer it over "more configure.ac magic" -
but if this is what it takes, I'm fine as well.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
