8.1.10 GA Release and Downloads

BGP templates with only '$URLS' would not work in any release.

Added the ability to have NSProxy send RST packets for 'non-decrypted' deny decisions, so the browser does not retry the HTTPS request.

Customers transmitting old log files from "months" or "weeks" in the past could rotate out current logs depending on log file transmit ordering.

All [apiname]_count queries would load the entire data structure into memory causing possible memory limit exceptions to be hit with large datasets.

Client key in ClientHello can cause a fragmented ClientHello, which can cause the SNI name parsing to fail. Which can lead to the Policy Service to failing open, resulting in unfiltered requests.

The RAS service did not properly clean up IP Address entries from deployments with multiple DNS servers.

Added the ability to run Search Keywords on the HTTP Referrer in order to enable keyword blocking with YouTube.

RAS Service could create false 'address change' events for hosts that have both IPv4 and IPv6 addresses.

The RAS Service uses the fixed size array when merges old and new IP addresses that can be insufficient for multiple DNS servers polling.

We now trigger a log-only event when we detect 'decrypt://denied' but we do not get a corresponding HTTP request and the client connection is closed, (which indicates our CA certificate is not installed).

SysOps without Group General and Group Advanced permissions that allow for modifying a Group's information were still able to do so, due to the Group Lock feature added in the 8.1 release.

Fixed Polaris Report issues for the RAS service.

Exporting the Translation Catalog would include the WebAdmin HTML at the end of the file.

Administration > Translations > Extract Catalog would display a blank screen when exporting.

The Policy Service must set a Client Filter cookie to indicate which protocol is used, allowing the nMonitor API to parse and use the appropriate username.

The nMonitor API can no longer use the 'request information' without performing a Policy Service lookup to validate the case and other information.

Both Sysop and Admin Account users were unable to search the Groups list in the 8.1 release.

Sysops without List Permissions are able to modify the list settings because of the changes to assume identity which include loading their last page and breadcrumbs.

If you had the Category view set to both 'WebAdmin' and 'Reporter,' and you attempted to deselect one, your changes would not save.

If you disable the Protocol Detection Engine some traffic will not go into passthru mode properly and no Unknown Event will be triggered.

The nMonitor API did not respond with the 'OK:' response when we properly processed the event, returning an empty page instead.

NSUP2Date did not set the hostname for the service to send to the WebAdmin for improved validation.

Directory Sync will now only add the missing Accounts to the Groups and not replace all Accounts in the Groups during the Sync process.

libwebdb was not validating Account type correctly, potentially allowing Accounts to download information it did not have permission to access.

Report templates with custom Category filters added category numbers to the Report name errantly.

Parsing the X-Forwarded-For header for Client Filter processing could cause the Policy Service to restart.

Improved the ability to process CNS requests without adding any latency.

Profile Manager: When the user changes the categories for a profile, it won't set the category template, just changes the categories.

The Client Filter Exceptions List now encodes spaces to %20 in the entry, as the file we export to is space encoded.

Function iplist_ipv6_iprange_to_subnets could cause stack underflow when adding q.

The weekly Report date-dropdown list was inconsistent between the Report dropdown and the Report instance views.

Running the nsdctl chown nsd_* command could take a very long time to complete if the file sizes at the /usr/local/netsweeper/logs directory grew too large.

CNS servers resolving to IPv6 addresses can cause 7.2, 8.1 and 8.2 releases to abort. Customers should upgrade to 7.2.15, 8.1.10, and 8.2.3 to avoid future stability issues.