Release Notes Tanium Client (Version 7.4.7.1094)

Thank you for choosing Tanium. The following Release Notes document changes between releases of the Tanium Client.
The previous Tanium Client versions can be found here: Release Notes (Version 7.4.5.1225)

Tanium Client 7.4.7.1094

Release Date: November 2, 2021.

Special Notes

• Early access to ARM architecture installers including Apple Silicon Universal Binaries and Graviton are available upon request.

New Features

• The Tanium Client is now also built with support for Apple ARM architectures as Universal binaries.
• The Tanium Server API now offers the possibility of embedding configuration parameters like ServerPort and/ or proxy settings in an exported tanium-init.dat bundle, offering better coverage for non-default client installations.

Improvements

• Tanium Platform components now use OpenSSL v1.0.2za.
• The Tanium Platform components will now use Python v3.8.12.
• Platform components now use boost v1.75 libraries.
• The log rotation subsystem within Tanium components no longer spam their logs with repeated "Unable to remove log file" messages. This helps to keep I/O loads down during extreme low disk space conditions.
• The Tanium Client will now perform sub-process management for extensions from the main TaniumClient -d process, avoiding the possibility of process stacking.
• A Tanium Client will now reset its RegistrationCount every time it resets its ComputerID. This is a more desirable behavior when de-duplicating an endpoint's identity.
• The Tanium Client will now cycle through the IP addresses resolved for a Tanium Server or Zone Server in the order they are returned by the name resolution system in the operating system. This will allow the use of both IPv4 and IPv6 addresses as favored by the endpoint's configuration.
• When a ServerName resolves to both IPv4 and IPv6 addresses, the Tanium Client will first try to connect to the IPv4 targets.
• The Tanium Client will no longer log "Clear leader flag" at LogVerbosityLevel=21, which was too low and would spam the client logs with unnecessary information.

Bug Fixes

• Fixed the calculation of invalid and impossibly high Sensor runtimes which would appear in the Console displays.
• Added safeguards in both the Tanium Server and Client to fix the presence of invalid write_bytes values.
• The Tanium Server and Client now implement special safeguards to avoid invalid updates to Sensor stats data which have been found to poison the Sensor Runtime information stored and displayed in the Console. A new log file invalid-stats has been created to capture events when these stats are found to be incorrect and keep a /metrics counter on the server for these invalid reports: tanium_sensor_stats_invalid_total.
• Changed a behavior in the Tanium Client where Manual Groups evaluation would be delayed and cause an Action to fail targeting an endpoint due to stale membership information.
• Fixed a bug in the Tanium Client by which it could stop reporting active Question result differences after its scheduled restart, possibly affecting its ability to report accurately on its Action completion statuses.
• Fixed a condition where the Tanium Client would prepend localhost to its ServerNameList when processing tanium-init.dat.
• Fixed a problem which would result in old private keys never being purged out of pki.db.
• Fixed a bug in the Tanium Client where it could sporadically crash while handling closing network connections.
• Fixed an issue in the Tanium Client where it would not close connections to peers when they were not in its peering lists anymore, making an endpoint appear as attempting to peer even when it was configured to be isolated.
• Fixed a behavior in Platform components where attempting to stop a process just after it exited naturally would unnecessarily spam logs with messages "Failed to terminate process" because the process was no longer there.
• Fixed a condition in the Tanium Client by which it would not persist the last execution times of Sensors through a client reset, causing the endpoint to have to re-execute every requested result on restart which would result in an increased number of [CRU] question results with every reset cycle.

Additional Information

None.

Known Issues and Workarounds

None.

Product Documentation and Resources

• Tanium Product Documentation
• Tanium User Research
• Software Updates and Announcements Signup