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).
nodejs · Jan 13, 2022 · bd52efe · bd52efe
1 parent 95c19c3
commit bd52efe
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;