Permalink
Switch branches/tags
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
837 lines (698 sloc) 36.1 KB
DigiDoc4J Java library release notes
------------------------------------
Release 2.1.0
------------------
Summary of the major changes since 2.0.1.RC.1
------------------------------------------
* Corrected validation of ASiC-E with implicit signature policy and TimeStamp
* Corrected error messages for integration tests
* Corrected support for trusted lists eIDAS parameters (TLWellSigned etc)
* Ensured that signature will not contain empty SignerRole tag
Release 2.1.0.RC.1
------------------
Summary of the major changes since 2.0.1
------------------------------------------
* Started to use DSS version 5.2 (sd-dss.5.2.d4j.3).
* Support to validate user certificate via OCSP has been added
Release 2.0.1
------------------
Summary of the major changes since 2.0.0
------------------------------------------
* In unit-tests the expired keys are replaced
* Unit-test for digidoc4j-util are fixed
* Added functionality for digidoc4j-util in order to test external signing
Release 2.0.0
------------------
Summary of the major changes since 2.0.0.RC.2
------------------------------------------
* Unit-test are refactored.
Release 2.0.0.RC.2
------------------
Summary of the major changes since 2.0.0.RC.1
------------------------------------------
* Added support for TLWellSigned parameter.
* Some refactoring in Signature classes and utilities.
Release 2.0.0.RC.1
------------------
Summary of the major changes since 1.0.8.beta.2
------------------------------------------
* Start of using semantic versioning (1.0.8 --> 2.0.0)
* Fixed validation of containers where mime type has wrong format.
* Added check that at least one data file is present before signing.
* Ensured that SignaturePolicyImplied element is not allowed in TM signatures.
Release 1.0.8.beta.2
------------------
Summary of the major changes since 1.0.8.beta.1
------------------------------------------
* Fixed signing with ID-card and using PKCS11SignatureToken when encryption algorithm is ECDSA and RSA.
------------------------------------------
Release 1.0.8.beta.1
------------------
Summary of the major changes since 1.0.7.2
------------------------------------------
* Started to use DSS version 5.1 (sd-dss.5.1.d4j.5).
* Added support for removing signature from container.
* Added support for creating, timestamping and validating the ASiCS containers.
* Added support for validating PADES containers (PDF-files with signature).
* Major refactoring of code
- classes from package org.digidoc4j.impl.bdoc are now in org.digidoc4j.impl.asic.asice.bdoc;
- the common functionality for ASiCE, ASiCS and BDOC are in package org.digidoc4j.impl.asic;
- the common functionality for ASiCE and BDOC are in package org.digidoc4j.impl.asic.asice;
- method DataToSign.getDigestToSign() is renamed to DataToSign.getDataToSign().
* Added new API methods for accessing signature validation details.
* Added support for BDOC validation warning when SHA-1 is used.
* Documentation (github wiki, javadoc in github) is updated.
Known issues
------------
* Signing with ID-card and using PKCS11SignatureToken class have still a problem
when encryption algorithm is ECDSA. We are working on it.
------------------------------------
Release 1.0.7.2
------------------
Summary of the major changes since 1.0.7.1
------------------------------------------
* Prevent XXE(XML External Entity) processing (switching to sd-dss-5.0.d4j.5).
------------------------------------
Release 1.0.7.1
------------------
Summary of the major changes since 1.0.7
----------------------------------------
* Fixed signing problem when encryption algorithm is ECDSA and signature profile LT_TM.
* Updated the pre-calculated policy digest value.
Known issues
------------
* Signing with ID-card and using PKCS11SignatureToken class have still a problem
when encryption algorithm is ECDSA and signature profile LT_TM.
------------------------------------
Release 1.0.7
------------------
Summary of the major changes since 1.0.7 RC.2
----------------------------------------
* Performance test fix
------------------------------------
Release 1.0.7 RC.2
------------------
Summary of the major changes since 1.0.7 RC.1
----------------------------------------
* BDocSignatureBuilder class has two new parameters - DEFAULT_SIGNATURE_PROFILE
and DEFAULT_SIGNATURE_DIGEST_ALGORITHM
* Fixed problem with missing jar's in digidoc4j-*-library.zip
Release 1.0.7 RC.1
------------------
Summary of the major changes since 1.0.7 Beta.2
----------------------------------------
* Fixed problem with OCSP responds where responseID is keyhash instead of name
* Removed logback.xml from jar file, it is needed only for digidoc4j-util
* Fixed problem in opening of DDOC files over stream parameter [#134342153]
* Added ability to configure network proxy and SSL settings through JVM parameters [#129040397]
Release 1.0.7 Beta.2
--------------------
Summary of the major changes since 1.0.7 Beta.1
----------------------------------------
* Changed TSL URL for Test mode
* Fixed problem with URI encoding for libdigidocpp
* Fixed problem with newline symbol in signature policy ID value
* In order to generate DSS validation reports the option '-r <reportDir>' for digidoc4j-util is added
Release 1.0.7 Beta.1
--------------------
Summary of the major changes since 1.0.6
----------------------------------------
* Started to use DSS version 5.0
Release 1.0.6
--------------------
There are no major changes since 1.0.6 RC.1
----------------------------------------
Release 1.0.6 RC.1
--------------------
Summary of the major changes since 1.0.6 Beta.2
----------------------------------------
* Project building system is now Maven
Release 1.0.6 Beta.2
--------------------
Summary of the major changes since 1.0.6 Beta.1
----------------------------------------
* Cleaned up repository and removed some unnecessary files [#114205179]
* API methods return empty object or exception instead of null where possible [#123022761]
* Reverted Bouncycastle libraries to version 1.54
Release 1.0.6 Beta.1
--------------------
Summary of the major changes since 1.0.5
----------------------------------------
* Updated dependency libraries to latest versions [#120674723]
* Corrected error message in case of invalid DDOC file [#125515091]
* Added support for restricting special characters in data file names [#130206233]
* Reviewed and fixed unit tests where possible [#111599596]
* Signature getSigningTime returns trusted time (or computer time for BES) [#133662737]
* Writing Container directly to OutputStream [#133095765]
* Added changes to ignore some DDOC XML-file errors [#134342153]
* Validating Latvia xades signatures ocsp and timestamp diff [#128099395]
* Fixed invalid validation: EDOC 2.0 / SHA-256 signature: TimeStamp before OCSP-d.
Release 1.0.5
--------------------
Summary of the major changes since 1.0.4
----------------------------------------
* Implemented parallel validation of signatures in a container for better performance [#113606559]
* Added support for extending EPES signature to LT_TM profile [#130718495]
* Added support for CVC concatenated signature format for ECDSA signatures [#121930867]
* Added support for automatically determining if ECC signature algorithm [#121839585]
* Added support for setting SSL KeyStore and TrustStore parameters [#128759997]
* Upgraded DSS version to 4.7.RC2 [#130362923]
* Fixed including OCSP revocation errors in DSS simple report [#129526189]
Known issues
------------
* German and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.5 Beta 6
--------------------
Changes
-------
* Fix: Timestamp will not be taken when extending signatures from B_EPES to LT_TM [#132313731]
Known issues
------------
* German and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.5 Beta 5
--------------------
Changes
-------
* Fix: XAdES xml tag is added to the newly created signature and existing signatures are not changed [#132151975]
Known issues
------------
* German and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.5 Beta 4
--------------------
Changes
-------
* Fixed opening xades signatures without xml preamble [#131795201]
Known issues
------------
* German and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.5 Beta 3
--------------------
Changes
-------
* Implemented parallel validation of signatures in a container [#113606559]
* Upgraded DSS version to 4.7.RC2 [#130362923]
Known issues
------------
* German and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.5 Beta 2
--------------------
Changes
-------
* Added support for extending EPES signature to LT_TM profile [#130718495]
* Added support for CVC concatenated signature format for ECDSA signatures [#121930867]
* Added support for automatically determining if ECC signature algorithm [#121839585]
* Fixed including OCSP revocation errors in DSS simple report [#129526189]
Known issues
------------
* German and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.5 Beta 1
--------------------
Changes
-------
* Added support for setting SSL KeyStore and TrustStore parameters [#128759997]
* Improved OCSP request failure message with a link to the wiki Q&A section
* Fixed closing serialization streams
Known issues
------------
* German, Norwegian and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113](https://www.pivotaltracker.com/story/show/118940113)
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.4
--------------------
Summary of the major changes since 1.0.3
----------------------------------------
* Added support for filtering trusted territories being loaded from TSL [#109348844]
* Added support for PKCS#11 (Smart Cards, Hardware tokens) [#74204066]
* Added support for adding complete AdES (Raw) signature to a container [#74203228]
* Added network proxy configuration for http, https and basic authentication [#116952041]
* Added support for signing multiple files with the command line util tool [#118916203]
* Added support for B_EPES signature profile [#120656717]
* Updated DSS version to 4.7.RC1 [#119363039]
* Excluded logback dependency from built JAR [#118379881]
Known issues
------------
* German, Norwegian and Croatian TSL are being ignored for not being compliant.
* XML validation report has issues [#118940113]
* Validating old DDoc v1.0 signatures may have exceptions for having incompatible OCSP response.
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.4 Beta 3
--------------------
Changes
-------
* Added support for PKCS#11 (Smart Cards, Hardware tokens) #74204066
* Added support for signing multiple files with the command line util tool #118916203
* Added support for B_EPES signature profile #120656717
* Updated PKCS#11 signing example #116207301
* Fixed getting OCSP certificate when TSL was not loaded #121052217
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.4 Beta 2
--------------------
Changes
-------
* Added network proxy configuration for http, https and basic authentication [#116952041]
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.4 Beta 1
--------------------
Changes
-------
* Improved META-INF/*signatures*.xml file recognition [#118473567]
* Excluded logback dependency from built JAR [#118379881]
* Implemented adding complete AdES (Raw) signature to a container [#74203228]
* Improved signature type differentiation between BDoc-TM and TS [#118546083]
* Improved TSLCertificateSource.addTSLCertificate() according to new TSL standard [#109952664]
* Added load testing of signature creation and validation speed [#112669283]
* Fixed parsing bdoc-tm policy identifier
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
Release 1.0.3
--------------------
Summary of the major changes since 1.0.2
----------------------------------------
* Improved TSL loading and cache renewal (incl. lazy loading)
* Added support for Trusted List version 5 [#118240769]
* Data files are stored on memory with an option to store them as temporary files on disk [#80897454] [#80897454]
* Added recognition of Estonian older generation cards by using TokenAlgorithmSupport.determineSignatureDigestAlgorithm(X509Certificate certificate) [#101576478]
* Updated DSS to version 4.6 [#111596844]
* Fixed serialization [#116698977] [#117811871]
* Fixed ESTEID-SK 2015 certificate issues [#117057181]
* Fixed bugs
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
* 1 unit test is temporarily failing
Release 1.0.3 RC2 (Release Candidate)
--------------------
Changes
-------
* Fixed validating container data file names with signature references
* Excluded logback.xml file from the built jar file. It is included in the utility zip file, possibility to manage util logs [#118379881]
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
* 1 unit test is temporarily failing
Release 1.0.3 RC (Release Candidate)
--------------------
Changes
-------
* Fixed RESPONDER_CERT id attribute for OCSP certificates in signatures.xml file [#117057181]
* Fixed BDoc validation when opening serialized container [#117811871]
* Added UTF-8 as the ASIC container character encoding [#116681705]
* Added support for Trusted List version 5 (ETSI TS 119 612 v2.1.1) [#118240769]
* Improved error log when TSL loading fails
* Changed configuration so that signing OCSP requests is disabled by default in PROD (access certificate configuration is not set by default)
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
* 1 unit test is temporarily failing
Release 1.0.3 Beta 3
--------------------
Changes
-------
* Implemented cloning TSL for each signature creation and validation process [#117125475]
* Fixed serialization when opening existing containers [#116698977]
* Fixed getting signing certificate subject name [#115939015]
* Removed creation of digidoc4j.log file on disk [#116690151]
* Removed the requirement for configuring CA certs in yaml configuration for BDoc containers [#116690651]
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
* 1 unit test is temporarily failing
Release 1.0.3 Beta 2
--------------------
Changes
-------
* Implemented automatic renewal of TSL cache [#116461557]
* Implemented lazy TSL loading to speed up container opening when TSL is not needed [#114470853]
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
* 1 unit test is temporarily failing
Release 1.0.3 Beta 1
--------------------
Changes
-------
* Published version 1.0.2 to the Maven Central [#101127396]
* Merged DSS to version 4.6 [#111596844]
* Added recognition of Estonian older generation cards by using TokenAlgorithmSupport.determineSignatureDigestAlgorithm(X509Certificate certificate) [#101576478]
* Data files are stored only in memory by default [#80897454]
* Added an option to store data files as temporary files on disk [#80897454]
* by using DIGIDOC_MAX_DATAFILE_CACHED parameter when opening containers and
* by using LargeDataFile object when adding data files to a container
* Updated commons-collections to version 3.2.2
* Removed redundant dss-asic and dss-cades dependencies
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* When opening an existing DDoc container with DIGIDOC_MAX_DATAFILE_CACHED value set as 0, then everything is stored in memory. Data files should be stored on disk instead (a bug in jDigidoc)
* BES signature validation fails (reportedly no revocation data found)
* 2 unit tests are temporarily failing (mostly covering the known issues)
Release 1.0.2
--------------------
Summary of the major changes since 1.0.1
----------------------------------------
* Improved TSL loading time
* Improved performance on opening and validating BDoc containers [#94193396]
* Added support for creating multiple signatures in parallel and adding to the container later [#101575340]
* Added support for saving and opening containers without signatures [#74201980]
* Moved BDoc container handling from DSS to DigiDoc4j [#111598972]
* DSS signing library version was updated to 4.6.RC1 [#100649370]
* The old deprecated API is no longer supported by BDoc containers
* The more detailed changelog is available with the beta releases
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* BES signature validation fails (reportedly no revocation data found)
* 2 unit tests are temporarily failing (mostly covering the known issues)
Release 1.0.2 RC
--------------------
Changes
-------
* Renewed jdigidoc library to version 3.12.0 (for DDoc containers) [#105559614]
* Added support for the new Esteid CA (for DDoc) [#109958064]
* Added the new EU TSL signing certificates to the keychain [#112406999]
* Removed the old TSL signing certificates [#108620136]
* Optimized signature validation speed by using singelton Configuration objects [#94193396]
* Fixed generating random nonce for OCSP request for TS signature [#85883082]
* Fixed async signing and serialization [#112048907]
* Changed the default test TSL in TEST mode to demo.sk.ee [#112048093]
* Fixed validation of a different manifest XML namespace in manifest.xml file [#105651692]
* Added validation for not allowing signatures with CRLs to be valid [#105740878]
* Fixed opening containers with BOM symbols in mimetype files [#105652644]
* Fixed an exception when getting an invalid ocsp response [#111946527]
Known issues
------------
* Adding a raw signature to a DDoc container and then saving the container produces an error (a bug in jDigidoc version 3.12.0)
* BES signature validation fails (reportedly no revocation data found)
* 2 unit tests are temporarily failing (mostly covering the known issues)
Release 1.0.2 Beta 3
--------------------
Changes
-----------
* Finished moving Asic-e container manipulation from DSS to DigiDoc4j [#111598972]
* Many of the old deprecated API methods are not supported by BDoc functionality
* Improved the performance of opening and validating BDoc containers
* Default signature id is randomly generated (setting ID manually is still possible)
* Fixed setting BDoc validation warnings
* Solved the known issues reported in 1.0.2 Beta 2
Known issues
------------
* European TSL validation is failing [#112406999]
* 3 unit tests are temporarily failing (mostly covering the known issues)
Release 1.0.2 Beta 2
--------------------
Changes
-----------
* Moved Asic-e container manipulation from DSS to DigiDoc4j [#111598972]
* Added support for saving and opening containers without signatures [#74201980]
* Added support for setting signature encryption algorithm (e.g. ECC) in the signature builder [#110239246]
* The library version information is added for each file within the BDoc container as a zip comment [#74203294]
* Optimized the speed of signature creation [#84912270]
* Signatures can be created in parallel and added to the container later [#101575340]
* Fixed tsl scheme territory
Known issues
------------
* Serializing BDoc containers is not supported
* Extending BDoc container signature profile is not supported fully
* BDoc container validation report in XML format is not available
* The BDoc container is created from the scratch when saving an existing container (instead of just adding the newly added signature to the existing container)
* Default signature id is randomly generated by DSS (probably not a bug but a feature)
* European TSL validation is failing [#112406999]
* 22 unit tests are temporarily failing (mostly covering the known issues)
Release 1.0.2 Beta 1
--------------------
Changes
-------
- Fixed an error when OCSP response was missing
- Fixed handling OCSP revocation when reason is not given
- Fixed getting signature profile correctly for BDoc-TM signatures #104878462, #84684252
- Fixed TSL loading for test certificates - using country scheme 'EE' instead of 'EU'
- Fixed some unit tests
- Added missing dependency to the utility jar
Known issues
------------
- 2 unit tests are temporarily failing
Release 1.0.2 Alpha2
--------------------
Changes
-------
- Fixed 4.6RC1 upgrade problems #100649370
- Added validation if OCSP response is included after signing
- Validating BDoc-TM OCSP nonce
- BDoc-TM signatures without timestamp are also considered to have XAdES_BASELINE_LT level
- Validating OCSP production time and timestamp delta
- Adding library version as zip comment on BDoc containers
- Parsing BDoc manifest file
- Setting TSL socket timeout and handling LOTL loading exception
- Fixed signing with ecc signatures
Known issues
------------
- BDoc validation may not find all the errors
- 3 unit tests are temporarily failing
- Norwegian TSL can not be validated successfully
Release 1.0.2 Alpha1
--------------------
Changes
-------
- Upgraded DSS to version 4.6RC1 #100649370
Known issues
------------
- BDoc validation does not find all the errors
- BDoc container is missing zip comment with version info
- Not possible to sign with ECC certificate
- Clearing TSL cache does not work
- 35 unit tests are temporarily failing
- Many of the DSS unit tests are broken because OCSP response is required in BDOC
- Norwegian TSL can not be validated successfully
Release 1.0.1 BETA1
-------------------
Changes
-------
- Fixed: BDoc signing should fail when OCSP response is not received #108065658
- Fixed showing correct library version in OCSP and Timestamp request headers #107212346
- Added showing version information with the utility tool #107212346
- Added data file extraction to the utility program #108605834
- Confirmed Canonical XML v1.1 support #74213104
Known issues
------------
- 2 unit tests are temporarily failing
- Norwegian TSL can not be validated successfully
- Validation of signatures with older Estonian ID-card certificates produces warning: "The certificate is not qualified!" #105471148
Release 1.0.0
-------------------
Changes
-------
- Fixed forwarding OCSP signing configuration values to jdigidoc (DDoc containers) #108021558
- Hiding bloated TSL validation errors (Norwegian TSL is invalid) #108066580
- Fixed loading TSL validation keystore from a jar file.
Known issues
------------
- 2 unit tests are temporarily failing
- Many of the DSS unit tests are broken because OCSP response is required in BDOC
- Norwegian TSL can not be validated successfully
- Validation of signatures with older Estonian ID-card certificates produces warning: "The certificate is not qualified!" #105471148
Release 1.0.0.RC
-------------------
Changes
-------
- Fixed checking certificate validation when the signer's certificate is expired at the signing time (#86092592, #98721424)
- Added TSL signature validation (#98727714)
- Added possibility to enable/disable OCSP request signing
Known issues
------------
- 2 unit tests are temporarily failing
- Many of the DSS unit tests are broken because OCSP response is required in BDOC
- Norwegian TSL can not be validated successfully
Release 0.3.0 BETA6
-------------------
Changes
-------
- Added validation for checking if signature timestamp certificate is in TSL #83689768
- Generating nonce as "non-critical" in OCSP request for TS signature #105450476
- Made DDocContainer configuration thread safe #86696334
- Updated test TSL for a new one #101881124
- Fixed RSA signature digest algorithm prefixes #101138690
- Made logger declarations consistent
- Fixed signing existing DDoc container with the utility tool
Known issues
------------
- 2 unit tests are temporarily failing
- Many of the DSS unit tests are broken because OCSP response is required in BDOC
Release 0.3.0 BETA5
-------------------
Changes
-------
- Added validation for matching time-stamp with signature #98722280
- Added validation for the case when two data files are with same name and only one is signed #105211272
- Added including OCSP confirmation for DDoc LT_TM signatures #103395848
- Added validation check that OCSP response should be after time-stamp for BDoc containers #84683484
- Fixed removing signatures from the container #91601974
- Extracted BDoc container validation code into smaller classes.
- Fixed couple of failing unit tests
Known issues
------------
- 2 unit tests are temporarily failing
- Many of the DSS unit tests are broken because OCSP response is required in BDOC
Release 0.3.0 BETA4
-------------------
Changes
-------
- Updated Javadoc according to the new API [#103766598]
- Added validation support for RSA 2047 bit keys [#100938144]
- Fixed duplicate signature xml file exception when adding signatures to jDigiDoc container [#105288968]
- Renamed Signature.getRawSignature to getAdESSignature
- Improved logging
- Improved handling of empty OCSP response
Known issues
------------
- 7 unit tests are temporarily failing
- Many of the DSS unit tests are broken because OCSP response is required in BDOC
- DigiDoc4j UriEncodingTest and MultiSignatureThreadSafetyTest are broken because test signing certificate is expired
Release 0.3.0 BETA3
-------------------
Changes
-------
Fixed NullPointerException that occurred on DDoc containers when SignatureProductionPlace data was not provided
API improvements #102993198
- Container builder accepts DataFile objects
- Deleted DigestInfoPrefix class, moved prefixes to DigestAlgorithm enum
- Removed Container dependency from SignatureParameters class.
- Renamed Signature.getSigningTime to getClaimedSigningTime
- Renamed SignatureBuilder.withDigestAlgorithm to withSignatureDigestAlgorithm
- Removed Validating signature by validation type - Signature.validate(Validate validationType)
- Removed Signature.setCertificate
- Removed getting private key from signature token
- Added getting trusted signing time to the Signature interface
Known issues
------------
7 unit tests are temporarily failing
Many of the DSS unit tests are broken because OCSP response is required in BDOC
DigiDoc4j UriEncodingTest and MultiSignatureThreadSafetyTest are broken because test signing certificate is expired
------------------------------------
Release 0.3.0 BETA2
-------------------
Changes
-------
The new API is more backward compatible with the old API. Creating and opening containers is not backward compatible.
Added support for adding new container implementations in runtime
Changed test OCSP url
Updated unit tests with the new API
Reduced unnecessary logging a little bit
Known issues
------------
7 unit tests are temporarily failing
Many of the DSS unit tests are broken because OCSP response is required in BDOC
DigiDoc4j UriEncodingTest and MultiSignatureThreadSafetyTest are broken because test signing certificate is expired
Release 0.3.0 BETA
------------------
Changes
-------
Refactored API interface #102001330
Restored Logback logger configuration xml file #100946538
Fixed the bug when data files go missing in action when container contains more than two data files #100660808
Known issues
------------
API is not backwards compatible. Using it requires some changes to code.
9 unit tests are temporarily failing
Many of the DSS unit tests are broken because OCSP response is required in BDOC
DigiDoc4j UriEncodingTest and MultiSignatureThreadSafetyTest are broken because test signing certificate is expired
Release 0.2.20 BETA2
--------------------
Changes
-------
Fixed the interoperability problem with jDigiDoc: OSCP certificate tag has RESPONDER_CERT id
Included Nortal DDS team pull request to DSS and DigiDoc4j. Updated DSS libraries
Known issues
-------------
Many of the DSS unit tests are broken because OCSP response is required in BDOC
DigiDoc4j UriEncodingTest and MultiSignatureThreadSafetyTest are broken because test signing certificate is expired
IntelliJ IDEA project files are out of sync
Some files (DSSSignedInfo.java and DSSXMLSignature.java) were leftover after merging the pull request with DSS refactered code. Hopefully nobody will miss them
Interoperability with JDigiDoc: BDOC-TM (time-mark) files created with DigiDoc4j library can be validated with JDigiDoc version 3.10 or newer.
Release 0.2.20 BETA
-------------------
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 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 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.
Release 0.2.16
---------------------
- Support for handling ASiC-E XAdES (BDOC 2.1) digital signatures with time-stamps (denoted as LT level) and time-marks (denoted as LT-TM level).
- Support for handling DDOC (DIGIDOC-XML 1.3) digital signature formats.
- Support for using TSL (Trust service Status Lists) for obtaining trust anchor information.
- Possibility to create signatures with PKCS#12 tokens and add signature values that are calculated in external systems. e.g. via browser plug-in.
- Support for using RSA algorithm for cryptographic operations. ECDSA algorithm support will be added with the next iterations.
- ASiC-E LT-TM signatures (BDOC 2.1 with time-mark) that are created with DigiDoc4J library are not compatible with JDigiDoc library's versions 3.9 and earlier.
- Information about further developments can be found from Pivotal: https://www.pivotaltracker.com/n/projects/1110130. The library's API may be changed in the course of future developments according to feedback from users.