2 attachments
See matching posts in thread - WinHTTP Web Proxy Auto-Discover...
13_0.png
Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows - Microsoft Support
Overview When SEP first starts, it attempts to connect to SEPM without using a proxy. Regardless of the proxy setting the client always attempt to connect without a proxy first. If the client is unable to connect to any servers in its management server list, it will rotate its proxy settings...
3 Comments - I would have preferred it to use the winhttp local machine Proxy settings The SYSTEM account is an "user account" and should not be preferred over HKLM.* All our other systems are using WinHTTP local machine Proxy settings are not giving us problems Also see https://www-secure.symantec.com/connect/ideas/sepm-policy-configure-client-proxy-details "... as this does not allow for firewall/proxy exceptions ..."
MS09-013 Vulnerabilities in Windows HTTP services could allow Remote Code Execution (960803) CVE-2009-0086 ( BID 34435 ) Microsoft WinHTTP Integer Underflow Memory Corruption Remote Code Execution Vulnerability (MS Rating: Critical / Symantec Urgency Rating 8.3/10) A remote code execution vulnerability affects Windows HTTP services (WinHTTP API) due to how it handles certain parameters returned from a remote Web server
See matching posts in thread - Does this need to run as a user on the system or...
See matching posts in thread - Server is HTTP://liveupdate.symantecliveupdate.c...
See matching posts in thread - I recently encountered a case in which proxy inf...