Jump to content

howardagoldberg

Members
 View Profile  See their activity

  • Posts

    233

  • Joined

  • Last visited

  • Days Won

    2

Kudos

  1. Upvote
    howardagoldberg
    howardagoldberg gave kudos to somewheretodisappear in Android 10: Interesting Issue with Location, Permissions, and WiFi identification   
    I was having the same issue on a Pixel 2 after the Android 10 update. Permissions were set to Always. Disconnect/reconnect to home WiFi fixed the error.
    Thanx.
  2. Upvote
    howardagoldberg
    howardagoldberg gave kudos to MikeO3 in Android 10: Interesting Issue with Location, Permissions, and WiFi identification   
    Thanks for you help and quick response.
    1. Yes, it is Always.
    2. Yes, WPA2 personal (this is my home network WiFi)
    3. Disconnect & reconnect WiFi worked.
     
    Thank you for your suggestions as it appears to be resolved now after an scan and reviewing the audit summary.
  3. Upvote
    howardagoldberg
    howardagoldberg gave kudos to itman in HTTPS Monitoring   
    This is also worth a read and very much indicates that what Avast/AVG is doing is something Google doesn't approve of:
    https://techdows.com/2019/08/chrome-you-are-using-an-unsupported-environment-variable-sslkeylogfile.html
  4. Upvote
    howardagoldberg
    howardagoldberg gave kudos to itman in HTTPS Monitoring   
    Interesting article. I checked the environment variables for FireFox; I don't use Chrome, and Eset does not use or need to use this baloney.
    Both Avast and Kaspersky were having issues with use of their root CA certificates in Chrome a while back to decrypt SSL/TLS traffic. Appears this is Avast's solution to the problem and a very insecure one at that.
  5. Upvote
    howardagoldberg
    howardagoldberg gave kudos to Marcos in HTTPS Monitoring   
    We intercept network communication, decrypt the SSL communication (not all SSL communication) and encrypt it again after scanning. It's done in a safely manner; if there was a risk of data leak, we wouldn't do it.
  6. Upvote
    howardagoldberg
    howardagoldberg gave kudos to itman in ESET issue with Sandboxie - Persistent holding of registry keys   
    My cleaner module ver. is currently 1195 dated 6/10. I could have swore that it had been previously updated to 1198.
    Check what ver. your cleaner module is. If its not 1198, you will have to switch to pre-release updates to get it.
  7. Upvote
    howardagoldberg
    howardagoldberg gave kudos to Marcos in Modules 'Mismatch' on Windows 7 'vs.' Windows 10   
    It has nothing to do with the version of the program. It will be added through a module update soon.
  8. Upvote
    howardagoldberg
    howardagoldberg gave kudos to TomasP in 64-bit to 32-bit   
    Hello Howard,
    We are indeed in the process of switching from 32-bit modules to 64-bit modules.
    The 64-bit module are being tested and will be released via an update soon, so currently the app runs 32-bit modules, but there is full compatibility and full protection even on 64-bit systems and thus nothing to worry about.
    Now why you saw "64-bit" in the about screen earlier - this was simply a bug, which instead of the modules showed the bit-ness of the system. We fixed the bug in the latest release and now it correctly shows the bit-ness of the modules.
    Regards,
    Tomas
×
×
  • Create New...