The Netsweeper Client Filter 12.60 GA is now available for all customers. This release builds upon the stability and proven features of the Netsweeper Client Filter and provides customers with some major improvements for all operating systems. All customers are strongly encourages to upgrade to the 12.60 GA.
Summary of Features and Improvements
-
Chrome Client Filter MV3 nMonitor support!
-
Improved protocol parsing for SSL/TLS in Windows, MacOS, iOS VPN and Android VPN versions.
-
Updated the Client Filter Firefox Browser for both iOS and Android platforms.
-
Windows nUpdate software auto-upgrade improvements for better error handling and upgrade detection.
-
Improved Client Filter configuration storage on all platforms, increasing security and performance.
-
nMonitor engine is now included in the Client Filter installation and can be enabled and configured using the WebAdmin Client Filter Settings.
-
nMonitor offline event storage and replay has been improved on all platforms. Detections made while a device has no connectivity will be transmitted once the device has cloud access.
-
Chrome Client Filter improvements for nMonitor to allow for both keyboard logging as well as OCR based screenshots in MV3 and MV2 versions.
The Netsweeper Chrome Client Filter V3 Manifest is now available and includes nMonitor functionality. We are committed to making sure the new V3 Manifest is available with all features and this release marks functionality similarity between MV2 and MV3 for the Chrome Client Filter. Google has started to disable MV2 extensions, you can read more about this in their latest blog post, and can also see the Google Manifest V2 support timeline.
If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (support@netsweeper.com).
Downloads
Windows
MacOS
-
MacOS Client Filter All in One Profile (mobileconfig) 12.60.55.55
-
MacOS Client Filter System Extension Profile (mobileconfig) 12.60.55.55
-
MacOS Client Filter App Proxy Profile (mobileconfig) 12.60.55.55
-
MacOS Client Filter CA Certificate Profile (mobileconfig) 12.60.55.55
-
MacOS Client Filter Configedit MCX Settings Profile (mobileconfig) 12.60.55.55 Legacy (pre-Big Sur)
iOS
Android
Chrome
Changelogs 12.60
|
Issue Type |
Issue key |
Summary |
|---|---|---|
|
Bug |
CF-538 |
MacOS Client Filter could have issues when the server-side of a connection closed, potentially resulting in data from the remote server not being returned to the user application. |
|
Bug |
CF-543 |
The DUG message in the MV3 Client did not contain the GSuite enrolled user's email address. |
|
Bug |
CF-551 |
Resolved an issue where selecting the Client Filter 'Diagnostics' tool after a fresh install would result in the 'Workstation', 'Brand Name', and 'Client Filter Version' fields to be logged incorrectly. |
|
Improvement |
CF-552 |
We now include a 'mobileconfig generation tool' for the Windows and MacOS Client Filters, allowing customers to generate custom mobileconfigs with custom certificates. |
|
Bug |
CF-554 |
Resolved a Chrome Client issue where the Domain User Group message would not override the AssetID set in gSuite, which could cause issues with logging for nMonitor Events. |
|
Bug |
CF-555 |
Email, first_name, last_name, and workstation changes were not being detected by the Android Client, resulting in the DUG message not being sent. |
|
Improvement |
CF-557 |
The Client FIlter ConfigEdit parser now supports both single and double quotes around arguments. |
|
Bug |
CF-558 |
The MDM/AppConfig configuration was not consistent between different platforms, iOS did not first apply the MDM Config when WebAdmin Settings were updated. |
|
Bug |
CF-561 |
If there was no 'confighash', the MV3 Chrome extension would corrupt the protocol and 'error out' resulting in either a 'fail open' or 'fail close' event. |
|
Bug |
CF-562 |
The '-c' argument was not clearing the 'first name', 'last name,' 'workstation,' and 'email' fields correctly. |
|
Bug |
CF-563 |
The '--workstation="workstation"' argument was not being applied in the Chrome MV2 Client. |
|
Improvement |
CF-564 |
Updated the Android Browser to use the Play Store's new SDK 'API Level 34' Target. |
|
Bug |
CF-569 |
Resolved a database error with the 'get last cookie' user/system service. |
|
Bug |
CF-573 |
There was no space in the generated config between the '--webadmin=' and the '--keyword_download_interval=' arguments. Also, the new '--kw-download-interval=' argument has been moved to the end of the config, for backward compatibility. |
|
Bug |
CF-574 |
The '-c' and '-s' arguments were not being enforced in Chrome builds, for either MV2 or MV3. |
|
Bug |
CF-575 |
Running the MacOS 'diagnostics' tool would cause the Client to crash if the Policy Server was set to version 8.2.6. |
|
Bug |
CF-577 |
The MV3 Chrome extension would display a blank page when visiting clever.com's Benchmark Education App page. |
|
Bug |
CF-579 |
Found an issue in the 12.50 Client where nUpdate would download the JSON and the MSI but would not install the downloaded MSI when an etag header was returned from the webserver. This has been resolved in the 12.60 release. |
|
Bug |
CF-580 |
The Chrome MV3 12.50 Extension was causing YouTube to crash and become unresponsive. |
|
Improvement |
CF-583 |
The nmonitor_offscreen.html module did not always load, which could result in nMonitor failing to start. |
|
Bug |
CF-587 |
The Chrome MV3 Service worker could become inactive causing issues with nMonitor and Filtering triggers. A new Keep-Alive method for our service worker has been added to Chrome MV3 extension. |
Copyright © 2024 Netsweeper Inc. All rights reserved.
Confidential and Private information. Distribution of the information contained herein is strictly prohibited.