Results 1 to 5 of 5

Thread: Security (97)

  1. #1
    4 Star Lounger
    Join Date
    Mar 2001
    Location
    New Zealand
    Posts
    541
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Security (97)

    I am running Office 97 on Windows 98SE. Also running Kerio Personal Firewall. I sometimes get an outgoing message alert from Kerio saying the MSOffice Shortcut Bar is trying to contact crl.verisign.com. Also that Windows Explorer is trying to do the same thing.

    Why should these two programs want to be doing that and should I allow it or deny it?

  2. #2
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security (97)

    Nothing MSKB. Try Kerio KB Search.

    SMBP

  3. #3
    Platinum Lounger
    Join Date
    Nov 2001
    Location
    Vienna, Wien, Austria
    Posts
    5,009
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security (97)

    Requests from Windows Explorer are commonly picked up by firewalls. They are usually to contact some part of Microsoft - commonly regarding search. Some freeware firewalls also tell you the IP address and name (if available) of the site that a device is trying to contact.
    Gre

  4. #4
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Security (97)

    VeriSign is the largest certificate authority in the known universe. Any time you visit a secure site, or load a "signed" Office add-in, there is a good chance that your computer will try to verify the certificate, and almost all roads lead back to VeriSign. I'm not certain, obviously, that this is what's going on, but it's my best guess. See if you can correlate the warnings with those kinds of activities.

  5. #5
    Platinum Lounger
    Join Date
    Jan 2001
    Posts
    3,788
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Security (97)

    This looks like an issue with expired Verisign certificates (which is also causing other problems as mentioned in other posts). See Slashdot for details.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •