Ask a Question

News ID : NEWS10071

INFORMATIONAL | Discontinued Use of (Legacy) SHA1 RFC 3161 timestamp service

By April 18, 2017, Symantec will decommission the "Legacy" timestamping service.

(Legacy) RFC 3161 SHA128 Timestamp Service:

To support business continuity for our customers, we have provided the following replacement services.

(New) RFC 3161 Service SHA256:

Important: Customers must leverage SHA256 Timestamping service going forward, and should not use a SHA1 service unless there is a legacy platform constraint which doesn't allow use of SHA2 service (in this case you can use this new URL: RFC 3161 Service SHA128:

Background and Key Industry Mandates affecting the Timestamping services

  • To comply with Minimum Requirements for Code Signing (CSMRs) published by CA Security Council and Microsoft Trusted Root Program Requirements (section 3.14), Symantec has set up the "new" RFC 3161 (SHA1 and SHA2) service as per specifications and requirements laid out by section 16.1 which requires FIPS 140-2 Level 3 key protection.
  • In the near future, Oracle will be taking steps to remove SHA1 support for both Java signing and timestamping. This will not impact Java applications that were previously signed or timestamped with SHA1 as these will continue to function properly. However, Java applications signed or timestamped with SHA1 after Oracle's announced date may not be trusted.

If you need guidance on how to perform timestamping while signing Java Applications, please visit our Knowledge Base article for Java Applications.