Trouble with surf protection

Discussion in 'Prevx Releases' started by caiusilus, Feb 22, 2013.

Thread Status:
Not open for further replies.
  1. caiusilus

    caiusilus Registered Member

    Joined:
    Feb 14, 2013
    Posts:
    35
    Location:
    France
    Hi,

    there seems to be an issue with surf protection... When webroot flaggs a site, even if I decide to block, the site continue loading, nothing is blocked.

    regards,
    Laurent
     
  2. pegas

    pegas Registered Member

    Joined:
    May 22, 2008
    Posts:
    2,016
    Yes, that's the known issue on which Webroot is working on. However the fix won't be so quick as they're revamping the Web Shield to better accommodate in to browsers. Anyway you're still protected because other modules of WSA are on duty.
     
  3. caiusilus

    caiusilus Registered Member

    Joined:
    Feb 14, 2013
    Posts:
    35
    Location:
    France
    Hi Pegas,

    thanks :)
     
  4. GrammatonCleric

    GrammatonCleric Registered Member

    Joined:
    Jan 8, 2009
    Posts:
    372
    Hmm I don't know about that. How do you define being protected?
    If the site block is via URL and not the actual content then you get the URL is blocked but if the content loads then it will still infect you if the given code piece has not yet been detected.
    Yes we get the normal shpiel of "well everything that's loaded is being monitored and will be removed once it's detected" now here is the rub.

    It will be remove ONCE IT'S DETECTED. What if it's not detected? What if it's detected 5 days from now and meanwhile it was sitting resident running on your system and collecting all the data it wanted? What if you decided to pay your bills within those 5 days? And also from the previous threads in this forum the total removal is not guaranteed once the infection takes hold.
     
  5. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    Even if it doesn't block the website from loading, WSA will block any code coming from it while it's active. It basically enters into a "no untrusted code can execute whatsoever" mode coming from the browser or any sub-process so in the event that we don't close the website or if it loads from an ad/etc., you're still protected.
     
Thread Status:
Not open for further replies.