Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Studio
  4. Signing ClickOnce manifest, valid timestamp servers

Signing ClickOnce manifest, valid timestamp servers

Scheduled Pinned Locked Moved Visual Studio
questionsysadmincryptographyhelp
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    RalfRider
    wrote on last edited by
    #1

    Hallo guys, when creating an assembly, a ClickOnce manifest is can be created. This requires an X.509 certificate and a timestamp server. After adding a certificate to the certicate store, the assembly is created without error or warning. So, what is the purpose of a time server and where do I get a the url of timestamp server? Thanks, Ralf

    F 1 Reply Last reply
    0
    • R RalfRider

      Hallo guys, when creating an assembly, a ClickOnce manifest is can be created. This requires an X.509 certificate and a timestamp server. After adding a certificate to the certicate store, the assembly is created without error or warning. So, what is the purpose of a time server and where do I get a the url of timestamp server? Thanks, Ralf

      F Offline
      F Offline
      frm19
      wrote on last edited by
      #2

      Hi Ralf, ClickOnce Manifest Signing suggests http://timestamp.verisign.com/scripts/timstamp.dll which is working. Others are http://www.trustcenter.de/codesigning/timestamp http://timestamp.globalsign.com/scripts/timstamp.dll http://timestamp.comodoca.com/authenticode and succeed using Microsoft signtool.exe, version 4.00. Many more CAs should run servers, a least each root CA. X509 certificates for Authenticode require a higher degree of trust if manisfests get a time stamp at creation time. EricLaw mentions this in Everything you need to know about Authenticode Code Signing A signed, time-stamped package remains valid indefinitely, so long as the timestamp marks the package as having been signed during the validity period of the certificate. It may be state in MSDN somewhere. frm19

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups