-
Notifications
You must be signed in to change notification settings - Fork 39
Signing a customised assistant makes it unusable #35
Copy link
Copy link
Open
Description
When code-signing a customised assistant, the newly signed exe does not recognise the (embedded) msh file anymore and thus cannot connect to my server.
Debug output:
17:13:.7140: ***** Starting MeshCentral Assistant *****
17:13:.7172: Version 0.1.8175.21599
17:13:.7182: Set TLS 1.2
17:13:.7196: InitializeComponent()
17:13:.7961: Checking for embedded MSH file
17:13:.8266: Check for built-in agent
17:13:.8306: Get list of background agents
17:13:.8612: MainForm_Load()
17:13:.9161: connectToAgent
17:13:.9230: Agent: ConnectPipe()
17:13:.9262: Agent: ConnectPipe() - failed
17:13:.9176: Agent: ConnectPipe()
17:13:.9199: Agent: ConnectPipe() - failed
It kind of works with an external msh file, but since I could only find an agent msh file, the assistant now lost the custom icon and name and is residing in the tray.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels