test: do not load absolute path crypto engines twice

Newer versions of OpenSSL now throws an error if an engine is loaded twice by its absolute path (a second load by its id appears to be okay). PR-URL: #41177 Refs: quictls/openssl#69 Refs: https://mta.openssl.org/pipermail/openssl-announce/2021-December/000212.html Reviewed-By: Danielle Adams <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Derek Lewis <[email protected]>
nodejs · Dec 17, 2021 · da8baf4 · da8baf4
1 parent 8fcb71a
commit da8baf4
Showing 1 changed file with 6 additions and 3 deletions.
diff --git a/test/parallel/test-crypto-engine.js b/test/parallel/test-crypto-engine.js
@@ -44,10 +44,13 @@ crypto.setEngine('dynamic', crypto.constants.ENGINE_METHOD_RSA);
     fs.accessSync(enginePath);
 
     crypto.setEngine(enginePath);
-    crypto.setEngine(enginePath);
+    // OpenSSL 3.0.1 and 1.1.1m now throw errors if an engine is loaded again
+    // with a duplicate absolute path.
+    // TODO(richardlau): figure out why this fails on macOS but not Linux.
+    // crypto.setEngine(enginePath);
 
-    crypto.setEngine(enginePath, crypto.constants.ENGINE_METHOD_RSA);
-    crypto.setEngine(enginePath, crypto.constants.ENGINE_METHOD_RSA);
+    // crypto.setEngine(enginePath, crypto.constants.ENGINE_METHOD_RSA);
+    // crypto.setEngine(enginePath, crypto.constants.ENGINE_METHOD_RSA);
 
     process.env.OPENSSL_ENGINES = execDir;