NOD32 signature update

Discussion in 'NOD32 version 2 Forum' started by whistl3r, Sep 5, 2005.

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

    whistl3r Registered Member

    Joined:
    Apr 7, 2005
    Posts:
    69
    Recently I noticed that NOD32 marks it's last signature update according to your system time. So, for example, if for some reason you were to advance the time, let's say Septemeber 9, 2010, and NOD32 were to update within that time, then the signature files date will stamp it for that preciese date. Now if you change your system clock back and attempt to update NOD32, the signature files date will stay the same as when it was downloaded, in this case, Septemeber 9, 2010. You either have to wait till the next update or uninstall, reboot and install NOD32. :eek:

    I know it's a petty bug...
     
    Last edited: Sep 5, 2005
  2. RejZoR

    RejZoR Polymorphic Sheep

    Joined:
    May 31, 2004
    Posts:
    6,224
    Location:
    Europe/Slovenia
    I don't quiet understand what you want to say. But why would you want to change the clock anyway? And even if you do max time you'd miss the update would be 1 extra hour. And even that is very unlikely since it's a very very small chance that ESET would update at that exact moment...
     
  3. hadi

    hadi Guest

    I think he is trying to explain that if the last run of NOD update was 12.55PM and ESET team released an update by now say 1.00PM then NOD will propably update it self some time around 1.55PM (about an hour late)
     
  4. whistl3r

    whistl3r Registered Member

    Joined:
    Apr 7, 2005
    Posts:
    69
    updated to clear up some confusion.
     
  5. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    I can't see why this would be a bug.
    It simply tells you when NOD was updated (according to your system clock).
    The signature version and date still remains the same regardless of what your current date and/or time is.
     
  6. RejZoR

    RejZoR Polymorphic Sheep

    Joined:
    May 31, 2004
    Posts:
    6,224
    Location:
    Europe/Slovenia
    Well if thats the case i'd say all AVs do it this way. And thats why they're checking in 1 hour intervals (to lower the update miss gap between each checks). avast! (iPush System) and eSafe (i think) use remote update invoke system that pushes update to user rather than checking from client side.
     
  7. beetlejuice69

    beetlejuice69 Registered Member

    Joined:
    Mar 16, 2005
    Posts:
    780
    Is 02/09/05 the last time NOD updated or am I behind?
     
  8. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,624
    Location:
    Throughout the USA and Canada
    there hasn't been an update since then - so you're up to date it seems..
     
  9. Bubba

    Bubba Updates Team

    Joined:
    Apr 15, 2002
    Posts:
    11,271
    In our Updates Forum there is one listed for today.

    NOD32 - 1.1209 (20050905)
     
  10. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    Argh.. Sometimes I hate waiting for the sig information, I got other stuff to do :D
     
  11. beetlejuice69

    beetlejuice69 Registered Member

    Joined:
    Mar 16, 2005
    Posts:
    780
    OK guys thanks for the reply.
     
  12. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,624
    Location:
    Throughout the USA and Canada

    and if you use an update mirror of your own (provided by your company) - you can be up to 2 hours behind (almost).

    ;)
     
Thread Status:
Not open for further replies.