DSS Files

Bug fixes / Issues

• [DSS-3619] DSS Standalone fails to generate Simple and Detailed PDF reports
• [DSS-3637] DSS returns max validity time in the past for an expired timestamp created by a trust anchor
• [DSS-3648] Signature extensionPeriodMin is compromised by LT-level revocation data that requires revocation check
• [DSS-3651] Repeated DigestAlgorithmIdentifier in digestAlgorithms
• [DSS-3652] Incorporating an ER without a reducedHashTree in a CAdES signature
• [DSS-3655] Cryptographic suite validation is not aligned with RFC 5698 in case of conflicting constrains definition
• [DSS-3657] Validation of XMLERS with a renewed timestamp in XAdES

Improvements

• [DSS-3571] DSS Demos : add a link to download current validation policy
• [DSS-3585] Support of base64-encoded certificates on input fields within the demos
• [DSS-3620, DSS-3663] Deprecate NexU on signature creation webpages in the webapp, in favor of server-signing and dss-standalone
• [DSS-3645] DSS Standalone : add logback.xml support
• [DSS-3646] Align CAdES augmentation to re-use SignatureRequirementsChecker
• [DSS-3650] Provide more meaningful exception message on failed augmentation of a CMS signature with corrupted content
• [DSS-3661] Introduce DOMDocument
• [DSS-3665] Add file cache revocation sources with cache expiration based on nextUpdate field
(PR [#183] by @gustavoam-asdf)
• [DSS-3677] Upgrade commons-lang3 to version 3.18.0
• [DSS-3678] Upgrade json-sKema to version 0.24.0

+ All the changes included in DSS 6.3.RC1.

Migration

NOTE: This release includes breaking changes, impacting some functionalities, please see below:

• If you use a default validation process or provide a custom XML Validation Policy, the corresponding module should be added to the list of dependencies within your project:

  <dependencies> ... <dependency> <groupId>eu.europa.ec.joinup.sd-dss</groupId> <artifactId>dss-policy-jaxb</artifactId> </dependency> ... </dependencies>

• Two alternative implementations for CMS processing have been introduced, impacting various modules such as dss-cades, dss-pades and dss-asic-cades:

• dss-cms-object - Uses in-memory handling of CMS objects based on BouncyCastle classes. This implementation provides the "old" behavior familiar from previous versions of DSS. In order to use the module, it should be added to the list of dependencies as demonstrated below:

  <dependencies> ... <dependency> <groupId>eu.europa.ec.joinup.sd-dss</groupId> <artifactId>dss-cms-object</artifactId> </dependency> ... </dependencies>

• dss-cms-stream - An experimental implementation providing CMS reading and writing functionalities based on Streams. This implementation provides a possibility to sign and validate large documents, but the creation of CMS documents is limited to only BER coding format.

NOTE: Only one of the dss-cms-object or dss-cms-stream dependencies shall be used.

For more information about code changes and migration process, please refer to the Migration Guide in documentation.