List of fixes available in SGOS 6.5.9.8
B# |
Issue |
225616 |
After booting up, when the ProxySG appliance used IWA-Direct group-caching, the appliance retrieved incomplete domain information. |
231537 |
When the ProxySG appliance used IWA-direct authentication and SMBv1 was disabled, the appliance could not connect to the domain controllers. |
232467 |
When "selective authentication" was used over a Forest Trust during NTLM authentication, the ProxySG appliance might have experienced resets in the Schannel connection for an IWA-direct realm. |
B# |
Issue |
233014 |
The ProxySG appliance might have experienced memory pressure in SSH. |
234718 |
The ProxySG appliance might have experienced a watchdog restart in SSH. |
B# |
Issue |
228527 |
The ProxySG appliance might have experienced a restart in process group "PG_DNS" in process "DNS UDP Worker 164DDFBA90" in "libdnsproxy.exe.so". |
B# |
Issue |
232227 |
During a DNS update, if the ProxySG appliance was configured to report a health-state change for each IP address and health checks were disabled, the appliance might have reported a health-state change. |
232237 |
The ProxySG appliance might continue to send queries to a DNS server that has gone offline. |
B# |
Issue |
234133 |
ReqPrefetchCache and ReqRefreshCache HTTP heartbeat statistics always displayed a value of 0. |
234200
|
The ProxySG appliance experienced a page fault in process group "PG_HTTP" in process "HTTP SW C96C7EB90" for "2EE908B90" in "libforwarding.exe.so". |
234202 |
When decompression did not work on a posted GZIP file because the file was incorrect or invalid, the ProxySG appliance might have experienced a hardware restart in process group "PG_HTTP" in process "HTTP Decompressor Admin" in "libfdt.so". |
B# |
Issue |
233890 |
If you started a WebEx meeting during an ICAP response scan, the scan stalled at 99%. |
B# |
Issue |
232056 |
When archived configurations were saved to a file from the Management Console and then manually reinstalled from that file, the status message that displayed in the CLI contained HTML tags. |
B# |
Issue |
232982 |
The ProxySG appliance experienced a hardware restart at 0x3 in process "em.exe". |
B# |
Issue |
230934 |
If there was a new file downloaded for CachePulse, the ProxySG appliance could not install policy and displayed a "Connection to SG failed" error message. |
B# |
Issue |
227231 |
When the forwarding health check was set to verify the server certificate by default, the ProxySG appliance did not forward host health checks. |
B# |
Issue |
232927 |
When frequent SNMP bulk-requests were sent to the ProxySG, the appliance might have experienced high CPU spikes in SNMP. |
B# |
Issue |
232291 |
When the ProxySG appliance used SOCKS to send a file that was bigger than 4.2 GB, the rsbytes and sc-bytes were incorrect. |
B# |
Issue |
225974 |
Help text for the 'test hsm-keyring' command was incorrect. |
232549
|
When specifying the client negotiated cipher and server negotiated cipher, some supported ciphers were missing in the VPM GUI. |
233124 |
Using the 'test hsm-keyring' command to test an HSM that was unreachable caused the CLI to hang for 70-80 seconds. |
233732
234488 |
A new trust package was posted for this release. Review the following ALERT for further information: http://www.symantec.com/docs/ALERT2309 |
234492 |
When SSL proxy was enabled, Google Chrome version 50 could not access Google sites, such as https://www.google.com and https://www.gmail.com. Review the following ALERT for further information: http://www.symantec.com/docs/ALERT2323 |
B# |
Issue |
229636 |
HSM hostnames did not allow you to use the hyphen character in the hostnames. |
B# |
Issue |
210919 |
When a disk that had FAT partitions with more than 32768 sectors was added to the ProxySG appliance, the appliance might have restarted.
|
229073 |
After a restart, the ProxySG appliance might not have generated a core file. |