The Netsweeper Client Filter 11.10 EA is now available. This is the first release of the Client Filter 11 adding some initial higher risk improvements for both Windows and MacOS. The Netsweeper Client Filter 11 will be expanding our stable and proven Client Filter technology and introducing some new features and improvements over the next 6 months. Customers should upgrade to the 10 GA release, and for those waiting for the improvements listed in the release notes for 11.10 EA, they can consider testing these improvements and rolling them out to their production networks.
We anticipate rolling out many advancements and improvement to the Client Filter 11 over the next few months.
- Windows Update Service allowing customers running Windows to keep the Client Filter up-to-date from the WebAdmin interface with future expansion to MacOS
- Automated Client Filter device registration with the WebAdmin interface allowing for improved functionality
-
Improved internationalization support allows customers to easily install Windows in different languages
If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (support@netsweeper.com).
Return to the Client Filter 11x Release Notes page.
Previous Release and Next Release
Downloads
Windows
Mac
- MacOS Client Filter 11.10.54.54
- Mobile Config-Configedit_mobileconfig 11.10.54.54
- Netsweeper Client Filter - 11.10.54.54 mac64-tp_crt.pem
- Netsweeper Client Filter - 11.10.54.54 mac64-tp_app_proxy.mobileconfig
- Client Filter - 11.10.54.54 mac64-nmonitor_config.mobileconfig
- Netsweeper Client Filter - 11.10.54.54 mac64-configedit.mobileconfig
iOS
- Client_Filter_iOS_mdm-tunnel-11.10.1.unsigned.mobileconfig
- Client_Filter_iOS_mdm-tunnel-vendor-11.10.1.plist
- Client_Filter_iOS_mdm-tunnel-root-ca-10.50.1.pem
Android
- Netsweeper-android-11.10.54.54-work.apk
- Netsweeper-android-11.10.54.54-settings.txt
- Netsweeper_android-11.10.54.54-ca-root.pem
Chrome Web Store
Client Filter 11.10
Issue Type |
Ticket |
Summary |
|---|---|---|
|
Bug |
CF-138 |
Branding is added to the Chrome Client Filter MV3 version allowing customized builds for resellers. |
|
Bug |
CF-166 |
MacOS could attempt to use IPv6 DNS responses even though there were no IPv6 addresses available. |
|
Bug |
CF-168 |
When a WebAdmin Client Filter Brand had a password set to 'No Password', pressing Enter was still required when opening Filter Settings on the desktop. |
|
Improvement |
CF-170 |
The flags -f 1048576 for ring buffer support and -f 2097152 for improved proxy performance have been documented. |
|
Bug |
CF-171 |
Chrome MV3 did not do liger startup in the right order and cookies were overwritten. |
|
Improvement |
CF-177 |
The nsdivert.sys with ring buffers and ALE redirect has been enabled by default. |
|
Bug |
CF-179 |
The Windows MSI did not install when the Users or Administrator groups did not exist. This happened when Windows is internationalized. This issue impacted Client Filter 9.2 to 10.50 and is fixed in 11.10 and above. |
|
Improvement |
CF-180 |
When using Windows, in another language the divert config, or installer policy service popup gave an 'Invalid Catalog' error message. |
|
Bug |
CF-183 |
The old package from the Android txt file has been removed. |
|
Improvement |
CF-185 |
MacOS 11.10 and above improves detection of MacOS Assessment mode and network connectivity. The system extension will now fail open when an app enables assessment mode or there is no network connectivity and enables itself on any network event. |
| Improvement | CF-191 | The Client Filter configuration loading has been improved to avoid loading corrupt config data. |
|
Bug |
CF-193 |
The protocol engine could miss server name information in TLS packets due to over detection of SSLv2/SSLv3 when TLS packet Length was between 768 to 1023 bytes in length, causing SNI to not be properly parsed. |
| Bug | CF-194 | nMonitor detected the same word twice when repeats with a white space character like Puff Puff. or Puff Puff; or Puff Puff () this rare false positive detection issue has been resolved. |