Aare Nurm

Hello, Could you please send your signing certificate to [email protected] so we can analyze further. As background information: If you use default configuration then digidoc4j tries to access Estonian specific...

Thank you for your valuable input on debugging this problem. The fix has been added to the next release scope, which is currently planned in second part of May.

If LOTL or any required trusted lists (or all trusted lists) fail to refresh, new default handling will throw an exception which stops the processes that triggered the TSL refresh...

Thank you for your input on this topic. LOTL/TSL handling is a complicated process handled by multiple software modules. Since we are already in the release process of the version...

Digidoc4j 5.0.0 has now been released with changes in TSL loading. The original problem where refresh was not automatically retried when the first load failed (cache was still marked as...

I will close the issue as the 5.0.0 has been released for a year and no additional feedback has been given.

We have added this to backlog for investigation.

This proposal has been added to backlog for further analysis.

We have released Digidoc4j 5.0.0 where we have improved the stream usage in Digidoc4J side. However DSS 5.9 still uses byte arrays internally meaning that the maximum data file size...

Hello, Could you please clarify what do you mean by invalid signature? In example code you do not show actual signing. You just inserted random bytes (signatureBytes)?