SecureCircle Client Package Details
  • 25 Jun 2021
  • 3 Minutes to read
  • Dark
  • PDF

SecureCircle Client Package Details

  • Dark
  • PDF

Installed Package Details

When installed, SecureCircle will display as an installed package named “SecureCircle” across all desktop OS platforms, with versioning information in the following format:




Screen Shot 2021-06-25 at 1.44.18 PM.png


Screen Shot 2021-06-25 at 1.47.55 PM.png


Screen Shot 2021-06-25 at 1.49.10 PM.png

Installation Details:

Each installer is customer tenant specific. The installer will attempt to register the device with the customer’s own SecureCircle server by default.

Installer names which do not include the Invitation ID in the file will require additional parameters alongside the installer to register the device to the appropriate SecureCircle server.

Windows / Mac:

AD.InviteID.exe / AD.InviteID.pkg

  • When creating an automated deployment package for use in an Active-Directory environment, you can download the AD Installer from the SaaS tenant by navigating to Access Data > Devices and clicking on Download Application.

  • This installer automatically registers the SecureCircle agent with a configuration that relies on the logged-in user’s membership into Active Directory Security Groups for membership into Circles.

EMAIL.InviteID.exe / EMAIL.InviteID.pkg

  • When a user receives an Email-based invitation, they will receive a link for an installer which will automatically register the SecureCircle agent with your SaaS tenant, using the invitation ID generated by the Email invitation.

Mac Specific Instructions

  • For Mac devices, there are two additional installation steps which must be taken when installing manually (ie. not by MDM or other software deployment solution).
  • The installer will stop at the Validate section and prompt you to Open General Security Preferences. There will be a kernel extension from SecureCircle which needs to be allowed at this stage.
  • The installer will next prompt you to Open Privacy Preferences, where we will need to give the SecureCircle agent Full Disk Access. To do so, Select Full Disk Access from the left-hand menu. Then click and drag the fhagent icon from the SecureCircle installer into the list of apps which have Full Disk Access. You may then continue and the installation should complete successfully.

fhfs.exe / fhfs.pkg

  • In special cases, SecureCircle may provide a generic installer which is not customer tenant specific, likely named fhfs.exe or fhfs.pkg. Any installer that does not follow the earlier EMAIL.InviteID or AD.InviteID naming conventions will need to be installed from the command line with the following switches to register at install
  • /url={hostname of SecureCircle server}
  • /inv={InviteID}
  • Example: fhfs.exe / /inv=a1b2c3d4e5f6g7h8

Linux: /

  • is a script to help automate the installation of SecureCircle on a Linux device.

  • Sometimes the installer may be generically named, such as, and will need the following additional parameters to successfully install:


  • --tracker=

  • Example: sudo INVITATION_ID= a1b2c3d4e5f6g7h8 ./ --tracker=

  • Because the SecureCircle for Linux requires a specific kernel module for each different Linux kernel version, the script will access to SecureCircle’s repo for retrieving the appropriate kernel-level driver module. The device will need require access to the following hostnames:,

securecircle-version-Linux & securecircle-driver-version-Linux

  • In cases where using the script is not viable, SecureCircle can make the installation files (.rpm or .deb) available for installing the SecureCircle agent and SecureCircle driver components separately.
  • In order for SecureCircle to provide the correct driver module, two simple commands can be ran to check for a device’s OS & kernel version:
  • $ hostnamectl
  • $ uname -r

Process Names


The following are the SecureCircle process names for Windows:

  • fhagent.exe
  • fhuser.exe
  • fhtools.exe


The following are the SecureCircle process names for Mac:

  • SecureCircle
  • SecureCircle Finder Extension
  • fhshellext Networking
  • fhshellext Web Content


The following are the SecureCircle process names for Linux:

  • fhagent.bin
  • fhtools.bin

Network Access

SecureCircle requires access to port 443.

The SecureCircle agent will require network access to the SecureCircle Server via SSL (port 443). In most cases, either the hostname or IP Addresses of the SecureCircle Server can be added to any Firewall rules, or allowed lists of other network security tools, to ensure communication between the agent and server.

If installing on Linux, the installer may also need network access to the following hostnames:


Configuring Antivirus for SecureCircle

Information for configuring Antivirus and other security software to work with SecureCircle is available here.

Was this article helpful?