laarmy.blogg.se

Tarma installmate fails in windows 10
Tarma installmate fails in windows 10









tarma installmate fails in windows 10

  • Use CBC mode for PDF AES encryption and decryption even if the document requests Gallois Counter Mode (GCM).
  • PDF: Fixed rendering issue for fonts with Identity encoding which only uses one byte instead of two.
  • PDF: Fixed rendering issue caused by encoding glyphs wrong, fixed ZapfDingbats checkmark when not embedded and loaded by Java itself.
  • Avoid a NullPointerException when checking installed Java font as in some JDK versions the font configuration file is missing.
  • tarma installmate fails in windows 10

  • Fixed a bug parsing the signing date from the PDF signature annotation.
  • When validating a document with multiple signatures while =on then SecSigner will not break the OCSP check loop of if an OCSP status “unknown” occurs.
  • Allow Template as a normal type of a PDFPage.
  • Fixed bug sorting the PDF document versions if an xref offset had to be corrected.
  • Do not check the signature counter of a D-Trust M100 smartcards if an authentication signature is requested.
  • tarma installmate fails in windows 10

  • Workaround for a “connection not yet open” error message when calling the finish-URL of a SecSigner webrun start.
  • Handling of encrypted PDF documents improved.
  • Improved the SecSigner error message for not yet activated BNotK remote signature accounts.
  • Send a single signature request to the BNotK remote signature service which contains all hashes of the complete document batch.
  • SecSigner – Changelogs Current Version SecSigner 7.26 –











    Tarma installmate fails in windows 10