Skip to main content
Version: 4.50

Agent native messaging hosts

The Redtrust extension doesn't talk to the agent over the network. It uses the browser's native messaging mechanism instead: the browser reads a Windows Registry key that points to a JSON file, the host manifest, and that manifest declares which executable to launch and which extensions are allowed to talk to it. If either piece is missing, the extension still installs, but it never connects to the agent.

This page lists the values the agent installer writes on a Windows machine, so you can check the configuration of a specific machine. If your organization restricts native messaging through enterprise policies, see How to authorize Redtrust native messaging in managed browsers.

Registry keys​

The installer creates one key per browser. The default value of each key holds the full path to the matching host manifest.

BrowserHost nameRegistry key
Google Chromecom.redtrust.monitorhost.chromeHKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.redtrust.monitorhost.chrome
Microsoft Edgecom.redtrust.monitorhost.msedgeHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Edge\NativeMessagingHosts\com.redtrust.monitorhost.msedge
Mozilla Firefoxcom.redtrust.monitorhost.firefoxHKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\NativeMessagingHosts\com.redtrust.monitorhost.firefox

These are the values each key must hold in a standard installation:

BrowserKey value
Google ChromeC:\Program Files\RedTrust\RTExtensionExplorer\RTCHProcessExplorer.json
Microsoft EdgeC:\Program Files\RedTrust\RTExtensionExplorer\RTEdgeProcessExplorer.json
Mozilla FirefoxC:\Program Files\RedTrust\RTExtensionExplorer\RTFFProcessExplorer.json
Only under HKEY_LOCAL_MACHINE

The installer always writes these keys under HKEY_LOCAL_MACHINE. All three browsers also read the same paths under HKEY_CURRENT_USER, but the Redtrust agent doesn't create entries there. If a Redtrust entry exists under HKEY_CURRENT_USER, the browser uses it before the one under HKEY_LOCAL_MACHINE. If it points to an old or missing manifest, the extension can't connect to the agent. The agent installer doesn't create that entry.

When the installer skips the keys​

The installer creates each key only when two conditions are met:

  • The agent is installed in user mode: With AGENTMODE=SERVER, the agent doesn't register any native messaging host, because server mode doesn't use browser extensions.
  • The browser isn't excluded: Each entry depends on its own browser parameter, as listed in the following table.
ParameterEffect
NO_CHROME=1The installer skips the Chrome extension and its key.
NO_EDGE=1The installer skips the Edge extension and its key.
NO_FIREFOX=1The installer skips the Firefox extension and its key.
UNATTENDED_BROWSERS=1The installer skips every browser extension component in all three browsers, including all three keys.

See Agent installation parameters for the full list.

Host manifests​

All three manifests point to the same executable, C:\Program Files\RedTrust\host\RTExtensionHostNet.exe. What differs is the host name and how each browser declares the extensions it authorizes.

Chrome and Edge use allowed_origins, with IDs in URL form. Both browsers use the chrome-extension:// scheme, Edge included, so don't replace it with extension:// in the Edge manifest.

Chrome manifest (RTCHProcessExplorer.json):

{
"name": "com.redtrust.monitorhost.chrome",
"description": "RedTrust Monitor Extension Host",
"path": "C:\\Program Files\\RedTrust\\host\\RTExtensionHostNet.exe",
"type": "stdio",
"allowed_origins": [
"chrome-extension://pcicdcmhjogafcifkoimbfmpepdhnlje/",
"chrome-extension://ijdeibmhkjmgbjofgiaodomklfdnagdg/",
"chrome-extension://lofomkfpahkabmmocnnbmaaeooolmnlf/"
]
}

Edge manifest (RTEdgeProcessExplorer.json):

{
"name": "com.redtrust.monitorhost.msedge",
"description": "RedTrust Monitor Extension Host",
"path": "C:\\Program Files\\RedTrust\\host\\RTExtensionHostNet.exe",
"type": "stdio",
"allowed_origins": [
"chrome-extension://kchdcfmphcejeinpcbgkfaejlohfcflo/",
"chrome-extension://mdlfgfcdgbdpidpbomkpjamoadggabmi/",
"chrome-extension://ggfdlfhmdenmdecomcakhdhfdjjlnepa/"
]
}

Firefox uses allowed_extensions, with IDs in email address form rather than URL form. Firefox manifest (RTFFProcessExplorer.json):

{
"name": "com.redtrust.monitorhost.firefox",
"description": "RedTrust Monitor Extension Host",
"path": "C:\\Program Files\\RedTrust\\host\\RTExtensionHostNet.exe",
"type": "stdio",
"allowed_extensions": [
"rtffmonitor-extension@evolium.com",
"rtffmonitor-beta2-extension@evolium.com"
]
}

Extension IDs​

Each manifest authorizes several extension variants at once, so the host keeps working whether the machine has the published extension, the beta, or an older manifest V2 build. The EXT_V3 parameter determines which one is installed, but the manifest keeps all variants listed.

BrowserManifest V2Manifest V3Beta
Google Chromepcicdcmhjogafcifkoimbfmpepdhnljeijdeibmhkjmgbjofgiaodomklfdnagdglofomkfpahkabmmocnnbmaaeooolmnlf
Microsoft Edgekchdcfmphcejeinpcbgkfaejlohfcflomdlfgfcdgbdpidpbomkpjamoadggabmiggfdlfhmdenmdecomcakhdhfdjjlnepa

Firefox doesn't distinguish between manifest V2 and V3 in these IDs. It uses rtffmonitor-extension@evolium.com for the published extension and rtffmonitor-beta2-extension@evolium.com for the beta.

note

EXT_V3=1 is the default value and corresponds to the manifest V3 extension. Chrome and Edge have dropped manifest V2 support, so the IDs in that column only matter on older machines that haven't been updated yet.

Was this page helpful?