Jump to content

howardagoldberg

Members
  • Content Count

    159
  • Joined

  • Last visited

  • Days Won

    1

howardagoldberg last won the day on February 12 2018

howardagoldberg had the most liked content!

Profile Information

  • Location
    USA

Recent Profile Visitors

1,477 profile views
  1. Thoughts: 1) Is the permission for location set to 'always' or 'just when app is in use?' It needs to be set for always. 2) Are you certain that the WiFi network you are on is actually secure (WPA2 or better)? 3) After setting the location permission for ESET, toggle your WiFi off, let the phone connect to LTE, then turn the WiFi back on. I had to toggle the WiFi in order for ESET to 're-scan' the network I was connected to. Hope that helps!
  2. I just upgraded my Pixel 3 (Verizon Wireless) from Android 9 to Android 10 on my secured home network. Interesting issue encountered: After the update, ESET Mobile Security flagged my home network as an 'insecure public WiFi hotspot,' and recommended that I disconnect! Reason? ESET had not been given location permissions and therefore could not resolve the SSID of the network (even though I was connected to the WiFi). Giving ESET location permissions resolved the issue, no muss - no fuss. So, just as a heads up: If network aware apps aren't working correctly (security apps, WiFi/Network scanning apps, apps that sync over WiFi such as DejaOffice) after updating to Android 10, make sure you give those apps location permissions. As an aside, hopefully ESET folks will test this themselves, and roll out an update to account for this change in Android 10 so less savvy users do not become concerned that they are suddenly connecting to a non-secure public network from their home! 😉 @Marcos
  3. How does that compare to AVAST's method?
  4. I came across this article today via "Ask Woody" ... https://textslashplain.com/2019/08/11/spying-on-https/ The article specifically calls out AVAST, and I have not seen this warning in Chrome or other browsers (on the stable/release channel) using ESET. Can any of ESET's staff can comment on how ESET monitors HTTPS traffic, and if the 'issue' with AVAST is something ESET users need to be aware of vis-a-vis browser warnings/compatibility? Again, I've encountered no issues on this front ... I am simply curious! 🙂
  5. My cleaner module version is also 1195 dated 6/10. I don't use Sandboxie and no issues to report - just confirming that this module has not been updated on my systems (one Win10, one Win7). But based on @Marcos comment, this seems to be intentional.
×
×
  • Create New...