Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • The Code Signing tab contains two versions: Code Signing and EV Code Signing. The first form  

Code Signing is included in the contract between DigiCert and GÉANT

...

; the Extended Validation

...

version isn't. At the moment though and until the 1st of July 2015 The EV Code Signing certificates are made available for free as a 'welcome' from Digicert to the TCS members.


Image Modified

    The ordinary
    • For regular (non-EV) Code Signing
    order page suggests that different
    • orders, several Server Platform variants are available.
     In practice, "
    •  'Sun Java' should be selected in order to be
    selected
    • able to enter the CSR. The resulting certificate can be then used for other applications
    other than Java.
    Image Removed
    • as well. EV Code Signing
    using
    • certificates require a
    two-factor authentication token. During the period used Comodo Aladdin eToken Pro 32K (the blue stickje 'with the SURFnet logo) this is not suitable. Aladdin Pro 72K and
    • FIPS 140-2 hardware security module. Digicert requires either the Aladdin eToken Pro 72K or some SafeNet eTokens from the 5000 series
    well; they have in common that they are running Java Card and non Card OS.
    There is an extensive set of screenshots available on ordering and installing EV Code Signing certificates. Because there are many personal prevent those screenshots not this wiki. Ask for it at scs-ra@surfnet.nl if you want to get them sent.
    • ; older tokens not equiped with Java Card don't work.