Added option to not use TLS with connection to Intel AMT, usage is not recommanded.
Ylian Saint-Hilaire committed
Feb 1, 2022 at 16:08 UTC
b9b334e8a258a9f96d3b3ae9628a96ba45ea6106
2 files changed
+3
-2
amtmanager.js
+2
-2
@@ -533,7 +533,7 @@ module.exports.CreateAmtManager = function (parent) {
533
534
// Connect now
535
var comm;
536
- if (dev.tlsfail !== true) {
536
+ if ((dev.tlsfail !== true) && (parent.config.domains[dev.domainid].amtmanager.tlsconnections !== false)) {
537
parent.debug('amt', dev.name, (dev.connType == 1) ? 'Relay-Connect' : 'LMS-Connect', "TLS", user);
538
comm = CreateWsmanComm(dev.nodeid, 16993, user, pass, 1, null, ciraconn); // Perform TLS
539
comm.xtlsFingerprint = 0; // Perform no certificate checking
@@ -565,7 +565,7 @@ module.exports.CreateAmtManager = function (parent) {
565
566
// Connect now
567
var comm;
568
- if (dev.tlsfail !== true) {
568
+ if ((dev.tlsfail !== true) && (parent.config.domains[dev.domainid].amtmanager.tlsconnections !== false)) {
569
parent.debug('amt', dev.name, 'Direct-Connect', "TLS", dev.host, user);
570
comm = CreateWsmanComm(dev.host, 16993, user, pass, 1); // Always try with TLS first
571
comm.xtlsFingerprint = 0; // Perform no certificate checking
meshcentral-config-schema.json
+1
@@ -608,6 +608,7 @@
608
"additionalProperties": false,
609
"description": "Information passed to the AMT manager module that impacts all Intel AMT device managed within this domain.",
610
"properties": {
611
+ "TlsConnections": { "type": "boolean", "default": true, "description": "When set to false, MeshCentral will use TLS to connect to Intel AMT, this is not recommanded." },
612
"TlsAcmActivation": { "type": "boolean", "default": false, "description": "When set to false, MeshCentral will not attempt a TLS ACM activation on Intel AMT v14+" },
613
"AdminAccounts": {
614
"description": "List of username and passwords to try when connecting to Intel AMT.",