Jump to content

Scott PR

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Scott PR

  1. 16 hours ago, itman said:

    Chrome and FireFox use their own root CA stores to validate SSL/TLS communication. Eset copies its root CA certificate into those stores when it is installed. Edge and IE11 use the Win root CA store to validate SSL/TLS communication.

    If there was an issue in regards to Eset root CA certificate use, all HTTPS sites would have issues. Additionally when an Eset root CA certificate use issue manifest, the browser usually gives a notification in regards to a certificate issue. Are you receiving such browser alerts on these websites? If so, please post a screen shot of the alert being displayed.

    So...no, then?

  2. Having an odd issue: certain websites (facebook & microsoft in particular) are inaccessable from machines on our LAN. They are, however, accessable from our wifi, which is just ap's that feed the lan.  I noticed the ssl on one site was listed as "ESET Filter SSL CA" and was wondering, could there be an issue with our LAN accessing your root CA? Is that used as a proxy for other root CA's?

     

    Thanks

  3. Logged into the cloud admin today, saw all 132 of my machines have an outdated endpoint. Ok, no problem, click, select update installed products,check the version vs. what's installed (it's newer) select some non-essential machines, click "ok", click the list selected, click "ok", allow automatic  reboot" and I get an error "Failed to create task: The referenced repository package is not available"

     

    So I check the repository, it's not there.  Also, can't create an installer anymore, try to select a product, there are none.

     

    What gives? Is the new version not available?  Thanks

     

    Edit: So now it's working...agents are 64% updated. wierd.

×
×
  • Create New...