NOD32 Certificate

Discussion in 'NOD32 version 2 Forum' started by share98, Aug 24, 2007.

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

    share98 Registered Member

    Dec 5, 2004
    I am using Taskinfo to monitor my system. I have a message that says "A required certificate is not within its validitiy period when verifiying against the system clock or the the timestamp in the signed file."
    This is for NOD32 Kernel Service and NOD32 Control Center GUI.
    Sounds scary! What, if anything, should I concern myself with?

    NOD32 antivirus system information
    Virus signature database version: 2481 (20070823)
    Dated: Thursday, August 23, 2007
    Virus signature database build: 10627

    Information on other scanner support parts
    Advanced heuristics module version: 1.065 (20070802)
    Advanced heuristics module build: 1164
    Internet filter version: 1.002 (2004070:cool:
    Internet filter build: 1013
    Archive support module version: 1.057 (20070802)
    Archive support module build version: 1194

    Information about installed components
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
    Version: 2.70.39
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
    Version: 2.70.39
    NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
    Version: 2.70.39

    Operating system information
    Platform: Microsoft Windows XP
    Version: 5.1.2600 Service Pack 2
    Version of common control components: 5.82.2900
    RAM: 1022 MB
    Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992 MHz)
  2. FanJ

    FanJ Updates Team

    Feb 9, 2002
    Yep, I saw the same with the new TaskInfo on my XP-home SP2 Dutch.
    I too have been wondering about it and was asking myself whether something was wrong on my system.
  3. GAN

    GAN Registered Member

    Mar 3, 2007
    If you rightclick the files and select properties and then digital signatures you see the same thing. For some reason there is no signing time and this should normally be within the validity period of the certificate. It's a bit strange for a security company not manage to get it right. If the digital signature is correct you should easily see if the files is the original from eset or if it's been changed.
    So the message you see is normally something you should worry about, but for nod32 it's like this for the original files from eset and nothing much you can do about it. I think Eset should correct this though. It's useful when they manage to get the digital signature correct because then you could see using taskinfo or similar tools if the files been changed which normally is something you should worry about.
  4. FanJ

    FanJ Updates Team

    Feb 9, 2002

    Thanks! Yes, I knew about right-clecking the files and checking their properties.
    I'm not worried about the files themselves: my file-integrity-checkers will tell me when they're changed ;)

    I fully agree with you.
    It seems a little bit strange that ESET hasn't corrected this already.
    In fact I was hoping for an official reply from ESET (and I still do...).

    I'm glad that share98 posted about it here, because a posting by me quoting the Dutch warning would not help very much I'm afraid...

    Thanks again to both of you, and looking forward to an official ESET reply.

Thread Status:
Not open for further replies.