Sign Live! CC validation client
Sign Live! CC validation client
The workplace-based solution for
Signature verification
check
The following tests are included in the verification Sign Live! CC performed at least:
Supported ETSI signature and archive formats:
* The Evidence Record Syntax, ERS for short, is part of the specification of the Long-Term Archiving and Notary Service, LTANS for short. It describes the data format for an evidence file, the Evidence Record, which is used to provide evidence of the integrity of a document stored in a long-term archive.
The following functions are available after purchasing a Sign Live! CC License available:
The following product is available for the automatic validation and processing of large amounts of documents.
It should be possible to check whether a signature is valid, i.e. valid, even after many years. In order to be able to check a signature again, several pieces of information must be available:
To confidently answer these questions, a validation application such as Sign Live! several exams. An important aspect of this check are revocation checks using OCSP (Online Certificate Status Protocol), ie queries to the trust service provider (VDA) that issued the end user certificate used. In order for these OCSP queries to be carried out, this service must be made available online by the VDA (directory service). The replies from the VDA are in turn signed by the latter so that the trustworthiness can be checked and thus ensured. This is then done in turn with the inclusion of OCSP queries. International standards (ETSI) regulate how this is to be done in full. At the end of these queries, the validation application can then provide a trustworthy status of the end user certificate used.
But what if the necessary directory service is temporarily or permanently unavailable? A temporary disruption can occur if the required directory service is simply not available online. Or what if this was switched off by the VDA being discontinued? The central deletion of information after the retention periods have expired also represents a cut. The end user certificate used cannot be checked in such cases and therefore the complete signature check does not lead to a clear result.
LTV signatures are different. With this type of signature, all required information is embedded in the signature, again according to international standards (ETSI). In the case of PDF documents and signatures, this is technically regulated, for example, by the PAdES standard (ETSI EN 319 142) in the context of the PAdES-B-LT profile.
The necessary information can be embedded both when the signature is created and later during validation. However, it is rare for this to happen when the signature is created, since the time required to create the signature also includes the time required for verification. The enrichment of the LTV signature for validation before archiving is therefore a good idea. From this point on, the signature is always checked offline and takes place without access to the directory service. A check is therefore independent of the availability of this service, regardless of the reason why it is not available.
How the validity of certificates is checked is based on different models (chain, shell or modified shell model). These different models also make sense for the different uses of certificates. The validity of an SSL certificate should be checked differently in the browser than a certificate that was used to sign documents that have to be verifiable for decades.
Let's take Adobe Reader as an example. Adobe Reader will no longer classify a signature as trustworthy after the end user certificate used has expired, even if the signature was made during the validity period.
This behavior can be avoided by the LTV signature if the LTV signature is done before the expiration date. With the timely LTV signature, the Adobe Reader tick stays green and the signature continues to be positively checked - permanently. This is an important step on the way to greater user acceptance of the signature.
When trust centers switch to a new PKI infrastructure, it can happen that signatures that were created with very new signature cards are not validated. This is due to the fact that the new Trusted Lists (TSL) and/or Root CAs were not yet implemented when our software was released.
The Update of the trust lists in Sign Live! CC these signatures are validated again.
In server installations it makes sense to have the update triggered time-controlled. To do this, adjust the preconfigured service container service to be started.
Sign Live! CC starts with the language settings of the operating system.
To get the operating language of Sign Live! CC you need administrator rights to manipulate them.
Follow these steps:
By doing this, the entire user interface of Sign Live! CC presented in English.
To reset to German, delete the "SignLiveCC.exe.vmoptions" file from the bin directory and start it Sign Live! CC New.
To install the software on an Apple MacOS system:
To install a patch to an existing version:
For step-by-step instructions on downloading the software, installation and product activation, visit our Tutorials.
And get all the information about:
XIMA and procilon GROUP enter into a partnership Taucha, Dresden April 04.04.2023th, XNUMX – FORMCYCLE is a low-code application from the Dresden-based XIMA MEDIA GmbH, the administrations at
