Sign Live! CC client single
Sign Live! CC client single
The workplace-based solution for
Signature creation and signature verification
The workplace-based solution for
Signature creation and signature verification
sign
You would like to sign 25, 50, 100 or up to 1000 documents at the same time and at the same time only enter the PIN once?
The new BNotK card will be in Sign Live! CC supported from version 7.1.11
In future, the Federal Chamber of Notaries will provide its signature certificates via the remote signature service and no longer via a personal signature card.
The authentication for signature creation at the remote signature service is carried out using a personal smart card.
This requires a completely new procedure for signature creation. This signature is not triggered via the signature device "signIT smartcard CC", but via "signIT BNotK". When signing in the signature assistant, please select the appropriate signature device. If your signature certificate is not available, please contact the support of the Federal Chamber of Notaries.
If you are using a Reiner SCT card reader with an RFID function, you must switch off the RFID function so that there are no problems reading the authentication certificate on your card.
If you Sign Live! CC from a specialist application, please inquire with the manufacturer whether the new signature device has been connected.
The presentation of the signature can be designed individually. The procedure is in the tutorial "Design signature field display" described which you here available for download.
It is important to ensure that the last variable in the Appearance window contains a value. A newline as the last variable would lead to an error message (internal cryptographic library error).
For the qualified electronic signature you need in addition to the Software additionally a Signature card and a Card reader.
You can obtain signature cards from trust service providers (VDA). The of Sign Live! CC Supported signature cards and card readers can be found in our service description and system requirements.
Purchase the signature application software here Sign Live! CC for different operating systems.
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.
Are intarsys products affected by the security vulnerability?
The BSI has the following security warning published.
The actual problem is explained in a PDF, which is continuously updated on the BSI website.
You can find the following intarsys products in the supported versions continue to operate without changes:
The Java library that is causing the problem is in these products not .
This also applies to the Archisoft product from FHI-SIT in versions 1.1.1.8 and 1.1.1.9, which is sold by intarsys.
tom cat 9 does not use Log4j in its basic configuration without standard and other web apps.
Use the JVM in the required version (Java 11, SLcs gears: Java 8) at the most current patch level possible.
The Sign Live! CC / PDF / A Live! integrated JVM fulfills this (Java 11).
For Sign Live! cloud suite gears should be at least Azul JDK 8u312 + .
If you use software from Baqué & Lauter GmbH as a bailiff and with Sign Live! CC want to sign must in Sign Live! CC a certain "Service" to be set up.
If during the installation of the bailiff software the software Sign Live! CC was already installed, this service should have been set up automatically. Otherwise, this can also be done manually. You will find the corresponding instructions here.
When opening very large files, the Sign Live! CC The available memory is not sufficient (error message: ... "Java heap space"). The log provides information about the maximum memory Java requests from the operating system. Eg:
[2019.11.20-09:29:57.818][I][d.i.tools.logging][executor singleton][] maxmemory=477626368
First, check that the operating system can actually provide that much memory for Java. Operating system and other applications also require memory!
If enough memory is available, please gradually increase the memory claimed by Java.
So put in Sign Live! CC more memory available:
Important note:
1) The name of the vmoptions file depends on the operating system used.
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
