Cannot connect to AMT 9 after enabling TLS

[bwildenhain]

Hi,

I could use intel amt 9 via port 16992 with MeshCommander, but I enabled TLS and now it won't work using mesh commander.

I can connect using Firefox when enabling TLS 1.1 and it also works using

sslVersion = TLSv1.1
options = ALLOW_UNSAFE_LEGACY_RENEGOTIATION

to connect Firefox to an http socket using stunnel (running on my local host), but connecting mesh commander to localhost (with stunnel running) doesn't work. Is there an easy way set those TLS-options when using mesh commander?

I saw #111, but reverting to an unencrypted connection doesn't sound so tempting.

[si458]

You should simply be able to add a device and select use tls then it should connect without any problems, but i can't fully remember as all my stuff is managed by meshcentral for tls and amt, not meshcommander itself directly

[bwildenhain]

Thanks for your quick response! It also didn't work using meshcentral. I immediately got a timeout when trying to connect using MeshCommander. I used self-signed certs btw (created using MeshCommander).

[si458]

Have you tried factory testing the ant and setting up a fresh?
Generally I active amt then install Meshagent and let it activate amt correctly for me :)

[felinira]

I got it to work (although with a newer AMT version) by creating an openssl.cnf file in the current directory:

openssl_conf = openssl_init

[openssl_init]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
Options = UnsafeLegacyRenegotiation

and running with OPENSSL_CONF=./openssl.cnf node node_modules/meshcommander/