NOD doesnt scan SSL?

Discussion in 'ESET NOD32 Antivirus' started by Hecke, Sep 7, 2010.

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

    Hecke Registered Member

    Joined:
    Sep 7, 2010
    Posts:
    2
    Hey mates,
    I am using Eset Smart Security, but I now saw, that it fails the test with the EICAR-Test-file in Secure Sockets Layer-encrypted-connections?

    Code:
    http://www.eicar.org/anti_virus_test_file.htm#
    Is there any way I can enable HTTPS-scanning?

    I also noticed this:
    http://www.abload.de/image.php?img=unbenanntycfb.png

    Thanks :)
     
  2. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    are you using the latest version? try it if not in case it makes a difference.
     
  3. Hecke

    Hecke Registered Member

    Joined:
    Sep 7, 2010
    Posts:
    2
    I am using version 4.2.64.12


    Thanks for your reply - so that is not normal?
     
  4. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    it is working, but you need to enable SSL scanning - judging by your screenshot it is not, perhaps check pruefen von anwendungsprotokollen

    07-09-2010 20-31-07.png
     
  5. volvic

    volvic Registered Member

    Joined:
    Aug 17, 2009
    Posts:
    220
    why is this not turned on by default?
     
  6. volvic

    volvic Registered Member

    Joined:
    Aug 17, 2009
    Posts:
    220
    Does it mess up normal browsing? I just turned it on and the reply got stuck at 'posting reply' I turned it off and the reply posted.
     
  7. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    depends on the browser, does not work with FireFox on SSL/TLS, else it should not have a negative impact on the browsing experience. you have to have all browser closed for turning it on, due to propagation of the Eset root certificate. If however any browser open NOD would issue a warning. Perhaps the reason for getting stuck
     
Thread Status:
Not open for further replies.