Skip to content

Releases: open-eid/digidoc4j

Release 0.2.20 BETA

02 Jul 10:23
Compare
Choose a tag to compare
Release 0.2.20 BETA Pre-release
Pre-release

Release of version 0.2.20 BETA

Please note that this is an eID software beta version.
The software may not work properly and some faults may occur.

Changes

  • DSS has been updated to version 4.4.RC1
  • DSS did a major refactoring of modules and some changes to API
  • Fixed unit tests and code that broke because of DSS rafactoring

Known issues

  • Interoperability problems with jDigiDoc:
    • OSCP certificate tag is missing RESPONDER_CERT id in signatures.xml file when BDOC is created with DigiDoc4j, but jDigiDoc requires that ID to be present. Note that RESPONDER_CERT id is not required by the BDOC standard.
    • BDOC-TM (time-mark) files created with DigiDoc4j library can be validated with JDigiDoc version 3.10 or newer.

Release v0.2.18

14 Jan 10:59
Compare
Choose a tag to compare
Release v0.2.18 Pre-release
Pre-release

Release of version 0.2.18

New:

  • It is possible to set TSL loading connection timeout
  • Signing certificate digest method is SHA256 instead SHA1
  • Generates random nonce for OCSP request for TS signature

Fixes:

  • Bad error message (No revocation data for the certificate) for revoked OCSP replaced with "The certificate is revoked"
  • Now is restricted to add 2 data files with same name from stream.

Known issues:

  • Interoperability with JDigiDoc: BDOC-TM (time-mark) files created with DigiDoc4j library can be validated with JDigiDoc version 3.10 or newer.

Release v0.2.17

07 Jan 15:32
Compare
Choose a tag to compare
Release v0.2.17 Pre-release
Pre-release

Release of version 0.2.17

New:

  • Verifies that the signature contains one signed properties reference
  • Supports signing with ECC signature

Fixes:

  • Signer's certificate validity now checked at OCSP response's produced at time
  • Revoked certificate now returns correct error message

Known issues:

  • Interoperability with JDigiDoc: BDOC-TM (time-mark) files created with DigiDoc4j library can be validated with JDigiDoc version 3.10 or newer.

More information can be obtained from Pivotal tracker: https://www.pivotaltracker.com/n/projects/1110130

Release v0.2.16

06 Jan 11:02
Compare
Choose a tag to compare
Release v0.2.16 Pre-release
Pre-release

Release of version 0.2.16

New:

  • Possible to create and validate BDOC time mark format documents
  • Ivy is used as dependency manager

Fixes:

  • Avoids SD-DSS to replace mime types known internally by extension
  • Order of signer roles, policy and signing location is not accordingly to XSD
  • OCSP nonce extension is non-critical
  • Sets manifest.xml file before signatures.xml in container
  • Signer's certificate must be valid at signing time (OCSP produced at / TS generation time)

Known issues:

  • Interoperability with JDigiDoc: BDOC-TM (time-mark) files created with DigiDoc4j library can be validated with JDigiDoc version 3.10 or newer.

More information you can get from Pivotal tracker: https://www.pivotaltracker.com/n/projects/1110130

Release v0.2-beta.13

04 Dec 11:20
Compare
Choose a tag to compare
Release v0.2-beta.13 Pre-release
Pre-release

Release of version 0.2-beta.13

New:

  • Possibility to configure allowed between delta time OCSP produced at and timestamp time
  • Implements retrieving timestamp time for ASiCE type type of containers

Release v0.2-beta.12

01 Dec 09:00
Compare
Choose a tag to compare
Release v0.2-beta.12 Pre-release
Pre-release

Release of version 0.2-beta.12

New:

  • Reduced verification time when container has been verified and not changed

Bugfix:

  • When OCSP certificate is missing from TSL, signature must be invalid

Release v0.2.11

23 Nov 18:41
Compare
Choose a tag to compare
Release v0.2.11 Pre-release
Pre-release

Release of version 0.2.11

NEW:

  • Removes datafile mimetype IANA check
  • When asic-e container with signature level T is opened it must be treated as LT level signature
  • Changes signature profile constants to more international
  • Adds verification that manifest and signature have the correct filename and mimetype specified

BUGFIX:

  • If container contains OCSP confirmation, this confirmation must be used