Chrome protection

Discussion in 'Prevx Releases' started by 800ster, Oct 25, 2013.

Thread Status:
Not open for further replies.
  1. 800ster

    800ster Registered Member

    Joined:
    Dec 1, 2006
    Posts:
    203
    I've noticed after the Chrome browser updates that WSA shows "new_chrome.exe", rather than "chrome.exe", under the Application Protection tab. As new_chrome.exe does not exist is the Chrome browser still protected? I think it is OK as I seem to remember reading somewhere that WSA protects based on hash values not filenames (and the padlock does show). Anybody confirm this please?
     
  2. Techfox1976

    Techfox1976 Registered Member

    Joined:
    Jul 22, 2010
    Posts:
    749
    Yes, and you are correct in your speculation. It protects based on file hash. It only records the first filename it sees for that hash locally, not the current location of the (or all) files that have that hash. So you were 100% correct and you're good to go. ^.^
     
  3. 800ster

    800ster Registered Member

    Joined:
    Dec 1, 2006
    Posts:
    203
    Thanks for confirming. It is confusing though on first glance, especially when you try to specifically add the application "chrome.exe" and it adds "new_chrome.exe" instead!
     
Thread Status:
Not open for further replies.