Re: About Digital Signature

From: Lars-Eric Gisslén (nowhere_at_inter.net)
Date: 05/27/04

  • Next message: Jan Kronsell: "Re: Access automation" 
    Date: Thu, 27 May 2004 23:19:42 +0200

    Wolff,

    I hope you bought the VBA/Office signing certificate. If you recieved two
    files, *.SPC and *.PWK then you have got the code signing certificate for
    EXE, DLL, CAT, CAB, ... files

    If you have got the correct certificate you can renew the certificate using
    your order number and Verisign will inform about one month before it's time
    to renew the certificate. You will however get a new certificate but with
    the same credentials as the old one. The old certificate has expired,
    litterally, and a new certificate has to be issued. This is a very simple
    process and nothing to worry about.

    Your macros will not recognize any signing but Word 2000 (and later) will.
    What is of interest is how the computers running your documents with signed
    macros will react on new documents signed with a renewed certificate. That
    is no problem. If the users has accepted to allways trust signed macros with
    your old certificate your new certificate will also be accepted so the user
    will not notice that you have renewed the certificate. However, if you buy a
    new certificate (not renew) then the users has to accept the new
    certificate.

    What is also very important is that you must timestamp your signing. If you
    don't, your clients will get into trouble when the certificate has expired.
    To enable timestamping you have to set the registry key:
    HKEY_Current_User\Software\Microsoft\VBA\Security\TimeStampURL
    to: http://timestamp.verisign.com/scripts/timstamp.dll

    Regards,
    Lars-Eric

    "Pocket von Tilo Wolff# ++" <camote2000@hotmail.com> skrev i meddelandet
    news:%239KvLWBREHA.1548@TK2MSFTNGP10.phx.gbl...
    > Hi, two questions
    >
    > I have a "Code Signing" type certificate I bought at Verisign
    >
    > The "Code Signing" type certificates can be updated without requesting a
    > brand new one?
    >
    > If it can be done, does my code (some Word's macros) recognize the new
    > certificate or it is necessary to specify the certificate again?
    >
    >
    >
    > Thanks
    >
    >

  • Next message: Jan Kronsell: "Re: Access automation"

    Relevant Pages

    • Re: Macro Certificates with Enterprise Server
      ... >> Just issue yourself a code signing certificate using the Windows ... Go to the web interface for certificate services ...
      (microsoft.public.windows.server.security)
    • Re: Certificate Trust List
      ... This posting is provided "AS IS" with no warranties, and confers no rights. ... I imported the CTL signing certificate in my ... >>Is the CTL signing certificate in your local profile? ...
      (microsoft.public.win2000.security)
    • Re: Certificate Trust List
      ... I imported the CTL signing certificate in my ... the personal certificate store on my ... domain controller. ... >Is the CTL signing certificate in your local profile? ...
      (microsoft.public.win2000.security)
    • Re: Certificate Revocation List (CRL) problem w/ Outlook XP
      ... the Signing Certificate using Outlook Clients. ... the Signing Certificate, the system fetches the Crl files to your Local ... If a Certificate found in the Certification Path has no CDP (Certificate ...
      (microsoft.public.security)
    • Re: Creating PKCS#7
      ... microsoft other then certificate store and another sample, ... >> that it doesnt contain the signing certificate I saw it in MSDN and it ... >> Muhammad Aftab Alam ...
      (microsoft.public.platformsdk.security)