Summary

Prerequisites and dependencies that are common to all client features and modules of the 1E Client.

Installation account for Windows

Installation account for non-Windows

To install the 1E Client on a non-Windows client the installation account must have privileges to run the sudo command.

1E Client supports only Tachyon client features on non-Windows devices. 





Supported platforms

Feature dependencies

Products and Features with dependencies on the 1E Client.

Firewall ports

1E does not provide a combined diagram showing all components and features. Please refer to the communications reference page for each product:

Anti-Virus and Malware

The following should be excluded from scans to prevent file locking and resource deletion.

  • 1E log files. See Log files.
  • The 1E Client temporary directory. We recommend modifying the TemporaryDirectory 1E Client configuration setting to %programdata%\1E\Client\Temp and excluding that directory. See 1E Client settings

    TemporaryDirectory must be specified as an absolute path. The directory is not automatically created by 1E Client. It must be created before being set otherwise 1E Client will use its default.



Digital signing certificates

On Windows computers, the installation MSIs, executables and DLLs of the 1E software are digitally signed by 1E using the 1E Limited SHA1 and SHA256 signature certificates.

These signing certificates are issued by the Symantec Class 3 SHA256 Code Signing CA, which in turn is issued by the root CA VeriSign Class 3 Public Primary Certification Authority - G5.

The SHA1 and SHA256 signature certificates are each countersigned with the same Timestamp signature certificate Starfield Timestamp Authority - G2, itself issued by Starfield Secure Certificate Authority - G2, in turn issued by the root CA  Starfield Root Certificate Authority – G2.

The root CA certificates (for signing and countersigning) must exist in the Third-Party Root Certification Authorities store (which is replicated in the Trusted Root Certification Authorities store). These root CA certificates are normally automatically provided by Microsoft's Update Root Certificates feature, however for legacy OS computers in a lab environment that are not connected to the Internet, see Constraints of Legacy OS.


Constraints of Legacy OS