MeshCentral
MeshCentral copied to clipboard
Consent box not showing in macOS agent
Hello,
I've stumbled into a weird issue with the macOS meshagent,
When I tried to take control with remote desktop over one of our Macbooks with the latest agent, our mesh central just waits for the acknowledgment of the consent of the client. With a yellow "Waiting for user access authorization..."
In the Client side, absolutely nothing shows up.
PS : The meshagent is correctly installed, others functionalities of the agent are working perfectly fine (like the power state) PS2 : The 2 needed authorization from the client is given for the meshagent (Accesibility and Screen recording)
Further analysis
When I was looking of the history of my terminal on the macOS client, I've stumbled into one of the commands that the meshagent executes :
/usr/local/mesh_services/meshagent/meshagent_osx64 -b64exec Y29uc29sZS5sb2coJ3RlbGwgY3VycmVudCBhcHBsaWNhdGlvbiB0byBkaXNwbGF5IGRpYWxvZyAiYWRtaW4gcmVxdWVzdGluZyByZW1vdGUgZGVza3RvcCBhY2Nlc3MuIEdyYW50IGFjY2Vzcz8iIHdpdGggdGl0bGUgIk1lc2hDZW50cmFsIiB3aXRoIGljb24gY2F1dGlvbiBidXR0b25zIHsiWWVzIiwiTm8ifSBkZWZhdWx0IGJ1dHRvbiAiTm8iIGdpdmluZyB1cCBhZnRlciB1bmRlZmluZWQnKTsgcHJvY2Vzcy5leGl0KCk7 | osascript 2>/dev/null | awk '{ printf "\x1e"; c=split($0, tokens, ","); split(tokens[1], val, ":"); if(c==1) { print val[2] } else { split(tokens[2], gu, ":"); if(gu[2]=="true") { print "_TIMEOUT_" } else { print val[2] } } printf "\x1e"; }'
If we analyse this command, we see that the meshagent execute an Apple script for what is suppose to be the consent box :
tell current application to display dialog "admin requesting remote desktop access. Grant access?" with title "MeshCentral" with icon caution buttons {"Yes","No"} default button "No" giving up after undefined
But this Apple Script returns an error which is "The variable undefined is not defined"
This is an issue for Bryan.
What os version is your macos running?
These tests have been done on OSX 12.4 and OSX 11.6
I'm also having this issue. OSX I have varies from device to device, but a couple of examples are 10.15.7, 12.4, and 11.6
Any update on this?
I think I found where the issue is coming from.. Working on it now... I think it may only need a server update...
Any update on this?
The fix for this was pushed with v1.0.75. Can you verify if you are still having this issue with the current release?
@si458 fixed can close