Open rgl opened 4 years ago
It's in the MeshCentral repository but it depends on custom node.js modules with names that conflict with existing modules and core modules. Those are in MeshAgent.
For meshcmd, if you grab the following files and put them in the same directory:
All files from meshcentral/agents/modules_meshcmd. The meshctrl.js file and meshservice.exe from here.
Then you can run:
meshservice.exe meshctrl.js
And you will see it's the same as running meshctrl.exe. In fact, meshctrl.exe is the just MeshAgent from MeshCentral with JavaScript appended to it. Hope that helps.
Thanks for the explanations!
Is the whole amt library contained in https://github.com/Ylianst/MeshCentral/tree/master/amt?
Does it make sense to convert it into a stand-alone node library (a separate repository/npm package) so it could be used by others?
@nomis, are you trying to port/incorporate/convert this amt library in https://github.com/nomis/intel-amt?
That repository just contains things I needed to do that MeshCommander couldn't like creating a server certificate without giving MeshCommander the Root CA private key. I also implemented KVM redirection because MeshCommander is mostly Windows-only and WebSocket redirection isn't currently working on Intel AMT 12.
It seems the amt library is at two places:
Which one is the canonical source code?
I ended up using the code from the first at https://github.com/rgl/intel-amt-toggle-power-example, but I'm not sure if I'm using the correct one.
I do not seem to find meshcmd in this repository nor in https://github.com/Ylianst?tab=repositories. Can you help me find its source code?