When is this problem with SSL scanning going to be fixed ?

Discussion in 'ESET Smart Security' started by tommy456, Aug 18, 2012.

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

    tommy456 Registered Member

    Joined:
    Jun 11, 2011
    Posts:
    137
    I have both win7 and XP o/s's after selecting the pre release update modules win7 no longer has the firefox 14.1 ssl /cert scanning issue resulting in all secure pages being blocked

    How ever on the xp side of things the situation has gone from it just being a firefox issue to it affecting all apps, everything gets blocked,

    The other day in trying to fix this problem, after switching to the pre release update modules, everything worked as it should,(same as win7) but after a breif period of browsing everything returned to being blocked, regardless of if the connection was HTTPS /SSL or un encrypted HTTP, so no scanning web protection whatso ever now on xp, the other thing that seems to be happening is EKRN.EXE will randomly crash, more so on xp, but it has done this on win7 whilst loading windows post boot, everything paused eset crashed and restarted

    On xp it seems to be linked with the physical memory acculmilation issue, I wish that they would fix this, forget the version 6 otherwise it will just be a rinse and repeat senario like some other rival vendors who end up with several broken versions of their products

    After some more testing,using a different user profile(win xp)this is what firefox reports with every secure web page after accepting the security cert for it http://i.imgur.com/e9oYf.png and after creating a exception in firefox this is how the page then loads http://i.imgur.com/VN1bI.png
     
    Last edited: Aug 18, 2012
  2. terradon

    terradon Registered Member

    Joined:
    Nov 5, 2006
    Posts:
    78
    Hmmm...it works correctly with win7, a current OS, but doesn't work in XP, an OS that is no longer supported by MS (except for security fixes). Why would any company spend time and money fixing an issue that only occurs when using an obsolete OS??
     
  3. tommy456

    tommy456 Registered Member

    Joined:
    Jun 11, 2011
    Posts:
    137
    Because they claim that it works on Windows XP, And not only that but believe it or not a hell of a lot of people still use XP and have no intention of switching to win7

    For those who have a lot of older games that were designed to run on XP ,Vista WIN7 just don't cut it, as they both do not support EAX or direct sound, sound acceleration, and there is no proper solution available, So there's just a few reasons there is going to be a market for security solutions for xp for some time to come,

    The SSL although now working(on pre release modules) on Win 7, could well in the future be broken again, SSL protocol checking has always been a little ropey never 100%
     
  4. dwomack

    dwomack Eset Staff Account

    Joined:
    Mar 2, 2011
    Posts:
    588
  5. tommy456

    tommy456 Registered Member

    Joined:
    Jun 11, 2011
    Posts:
    137
    Several times , and also tried earlier builds of v5, as it only affected Firefox when i used those builds previously,(Back when they were current)

    So it's down to some changes made once ess updates downloads the modules the same happens, infact the last earlier build that i tried things where actually worse, ekrn.exe crashing high memory, and totally broken SSL/HTTP/HTTPS scanning filtering
     
  6. wokkiedokkie

    wokkiedokkie Registered Member

    Joined:
    Nov 26, 2010
    Posts:
    10
    Location:
    Amsterdam, The Netherlands
    As of today, Firefox on my computer (Windows 7 Home Premium 64 bits) has this problem too, so it is not just Windows XP.

    Why is this a problem with FF only? Any news on when it is going to be fixed?
     
  7. bwb1

    bwb1 Registered Member

    Joined:
    Mar 20, 2010
    Posts:
    113
    Location:
    UK
    Yes it has affected W7 too. I have had to disable HTTPS protocol scanning weeks ago in order to see certain sites. (Certificate errors)
     
Thread Status:
Not open for further replies.