On Sun, 2020-06-21 at 10:53 +0200, Gert Doering wrote: > 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.Bottomley@HansenPartnership.c > > om> > > > > --- > > 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?
Could someone just test the proposed updated v6 patch on a Mac? https://sourceforge.net/p/openvpn/mailman/message/37031113/ If it works then we have something that functions on both platforms and we don't need to worry about windows until someone runs unit tests there. > 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. Right, that's what the patch in the url does: uses .so on both mac and linux. James
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
