12.50 GA Client Filter Release and Downloads (August 19th, 2024) – Netsweeper

Netsweeper is pleased to announce the Client Filter 12.50 GA release. After many iterations and major feature improvements the 12.50 release has received the GA milestone. All Client Filter customers are recommended to upgrade to version 12.50 GA. The 12.50 release adds major stability improvements and bug fixes in order to provide further stability to the all versions of the Client Filter. The v12 release updates protocol detection, improves Windows Registry change notification, has improved configuration and cookie storage for multiple users on all platforms, and further refines the nUpdate service to reduce bandwidth consumption. Netsweeper will be pushing the 12.50 release to the Chrome, Apple, and Android stores allowing customers to start taking advantage of the major improvements in the 12 Client Filter.

If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (support@netsweeper.com).

Downloads

Wndows

MacOS

iOS

Android

Chrome

Changelogs 12.50

Issue Type	Ticket	Summary
Bug	CF-438	The start.app.liger-event did not have the platform and OS on the Chrome Web Extension version.
New Feature	CF-496	nUpdate would repeatedly try to download the MSI from the same JSON update in perpetuity.
Bug	CF-501	Protocol URL parsing in the Client Filter Exception List was not always working, cuasing Local IP addresses to become inaccessible.
Bug	CF-503	iOS Browser would crash after closing a single tab in 12.10 to 12.40 (Upstream FireFox v118.1 issue).
Bug	CF-505	Setting excessively long max-value settings for Username, email, first name, last name, etc. could cause issues with Client Filter operations.
Bug	CF-506	When receiving invalid protocol data from a Client Filter startup event, we could not guarantee the event delivery to the Policy Service.
Bug	CF-507	Chrome options could be parsed as Integers and Floats instead of Strings, causing issues.
Improvement	CF-508	The Netsweeper brand will no longer prompt for the nMonitor configuration in the 12.X releases upon a fresh installation.
Bug	CF-510	The Chrome MV3 extension could use the default brand configuration while loading, causing issues with startup and configuration reload consistency.
Improvement	CF-511	The default Chrome brand will now use https://filter.cloud.netsweeper.com:3431, as cloud.netsweeper.com is now upgraded and supports TLS.
Bug	CF-518	Windows Registry monitor code was unreliable at terminating quickly when the service is stopped or restarted.
Bug	CF-519	Small memory leak was possible if we couldn't create a socket in the Client FIlter on Windows, MacOS, iOS, and Android.
Bug	CF-521	The iOS browser nMonitor version would continue to scan tabs after closing all tabs.
Bug	CF-526	The get_last_cookie_user was using wrong DB field name.
Bug	CF-528	The Domainusergroup (DUG) was not triggered when the gsuite configedit was updated.
Bug	CF-532	The Policy Service could not be changed via the GUI in Chrome MV2 12.40.
Bug	CF-537	DUG messages were not triggering immediately after changing the Policy Server via the GUI.
Bug	CF-539	An in-progress getconfig event was not clearing when the Policy Server or Brand information changed, potentially resulting in an incorrect Client name.
Bug	CF-541	Resolved an issue where the Windows Client Filter was not able to retransmit failed Event uploads.
Bug	CF-542	When running in Profile Manager mode, the Profile Manager password was not being accepted by Chrome when attempting to change the Policy Server information.
Bug	CF-546	System and User Cookies were out of sync, causing a loop of Liger Events.

How can we help?