It is not possible for the signature to be misused in the case of signotec products for signing PDF documents. This is thanks to the biometrics or the dynamic features of the signature. Where signatures are used, the image of the signature is inserted into the document, but this only serves as an optical endorsement. The unique, individual characteristics of the signer’s handwriting are also stored in the document. If an attempt is made to manipulate the signature, the image of the signature can be easily cut and copied, but the biometrics cannot. The biometrics are an essential component of the signature and are stored in the document in a highly encrypted manner. The document and the biometrics are inextricably linked, which means that any manipulation of the document itself or the signature can be reliably detected.
Therefore, two things have to be reliably protected:
- The document and
- the signature
The document must be protected against manipulation and the signature against (identity) theft. If only the image of the signature were to be captured, it would not be possible to reliably prevent the signature from being misused and there would be no legal or evidential security. signotec does not use any proprietary or manufacturer-specific format to create the electronic signature. In fact, signotec complies with the global Adobe PDF-ISO standard. Electronic documents signed using signotec can be checked at any time, anywhere and by anyone without technical input. For example, Adobe Reader can be used to check whether a document has been manipulated.
signotec only uses encryption and hash algorithms that have been classified as secure by the German Federal Network Agency. This list is available here. The mechanisms currently used include Blowfish 448, AES 256, RSA 2048 and SHA 256.
The signotec technology has also been tested by TÜV, the testing and certification organisation. signotec software and hardware complies with the TÜV ‘tested software’ specifications. After conducting a battery of tests during the TÜV inspection, no data could be injected into the transmission paths. Tampering with signed PDF files was picked up immediately and signalled clearly and explicitly. As stated in the test report: “The hardware and software function as a closed system. No security gaps were detected by the tester during testing. The tester was unable to find any obvious saved, unencrypted raw data during the test period.”
To ensure that the signature cannot be tapped into during capture via the signature pad, data transfer between the pad and PC is safeguarded in the case of the signotec Sigma and Omega pads. There are major differences in the driver technologies used here. We strongly urge customers not to use simple Wintab drivers or unencrypted data transfers.
Technical documentation can be provided once a non-disclosure agreement has been concluded.
Sure. The most common applications are available as a 30 days trial version. E. g. signoSign/2 can be downloaded after regestriation.
Firstly, a HID signature pad is also an USB device. The huge advantage of HID devices is that the driver integrated in Windows is used. This means that a USB driver does not have to be installed. Therefore, users dont have to deal with standby problems mode problems, changes in the USB port, irritating prompts to install drivers or the requirement that the software must be installed before a pad can be connected.
Software manuals are copied to the target computer during the installation and are accessible via the Start menu.
All user manuals and data sheets are available for download here.
There are two options to enable logging in SignoSign:
- Editing the ‘SignoSign.ini’ file in the SignoSign installation directory
- SignoSign option ‘Generate log file’
‘Toolbars’ --> ‘Menu – Generate log file’ must be disabled via the SignoSign configuration to ensure that this entry can be selected or enabled.
The ‘SignoSign_YYYY-MM-DD.log’ log files are saved under SignoSign Program DirectoryLog.
The content of the current log file can also be opened in SignoSign via ‘Options’ --> ‘Display current log file’.
The Omega and Sigma pads contain a service menu. This can be used to configure two device properties:
- The intensity of the backlight (Omega and BL-Sigma)
- The calibration of the sensor
The following FAQ will provide details on how you can access and use the individual menus.
The intensity of the backlight on the Omega pad and the Sigma pad can be adjusted.
In the case of the Omega, there are two levels of brightness (Medium/Maximum). In the case of the Sigma, there are 17 levels of brightness (Off – Maximum).
The backlight is basically supported in the latest components of the signoPAD API, but can only be switched between Off and Maximum. The intensity of the backlight can be easily adjusted using the integrated service menu.
The ‘Brightness’ service menu is activated by touching the upper right area of the sensor with the pen, while the device is being inserted into the USB port.
The service menu is available from firmware 1.12 (Omega) or 1.10 (Sigma) and, of course, only in Sigma devices with the backlight function. These can be identified by the product number ST-BL. See data sheet.
The sensor in Sigma and Omega pads can be calibrated. This may be necessary if the signature is not displayed precisely below the tip of the pen. We provide software for this purpose, please contact the signotec support team.
However, it is easier to do this using the integrated service menu.
The ‘Calibration’ service menu is activated by touching the upper left area of the sensor with the pen, while the device is being inserted into the USB port. Two crosses appear one after another and must be touched accurately using the pen.
The service menu is available from firmware 1.12 (Omega) or 1.10 (Sigma).
With Windows 8.1 and Windows 10, problems occured that the signotec HID pads turn off after a few seconds when beeing connected to the PC.
This is due to the introduction of a new power management in Windows 8.1 / Windows 10.
Devices with a power saving function, such as our HID pads, are unintended beeing put in standby mode.
Below you can find the download information for signotec HID driver without the power saving function.
signotec HID driver 32bit:
signotec HID driver 64bit:
Microsoft has published the following suggested solution:
Please see the following rewuired IDs for the signotec pads:
Please check in the general settings of the Acrobat Reader if the protected mode is activated.
Acrobat Reader X:
--> edit --> presets --> category: general --> activate protected mode at the start
Acrobat Reader XI / DC:
--> edit --> presets --> category: security (advanced) --> activate protected mode at the start
Deactivate protected mode if possible.
If, for any reason, this is not desired, there is still the possibility to allow certain applications via a Whitelist, even if protected
mode is activated.
For this purpose please perform the following configuration steps:
1. Activation of the Whitelist in the registry
- open the registry
- go to
- Generate a new REG-DWORD value with the name “bUseWhitelistConfigFile” and set the value to “1”
2.Generate a Whitelist-file
- generate the file “ProtectedModeWhitelistConfig.txt” in the installation path of the Acrobat Reader, for example “C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader”
- edit the generated text-file
; Files Section
FILES_ALLOW_ANY = %USERPROFILE%\*
PROCESS_ALL_EXEC = C:\Program Files\signotec\SignoSign\signotecPDFDocIDLoader.exe
PROCESS_ALL_EXEC = C:\Program Files (x86)\signotec\SignoSign\signotecPDFDocIDLoader.exe
PROCESS_ALL_EXEC = C:\Program Files\signotec\signoSign2\signoSign2.exe
PROCESS_ALL_EXEC = C:\Program Files (x86)\signotec\signoSign2\signoSign2.exe
REG_ALLOW_ANY = HKEY_LOCAL_MACHINE\SOFTWARE\Adobe
REG_ALLOW_ANY = HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe
REG_ALLOW_ANY = HKEY_CURRENT_USER\SOFTWARE\Adobe\Acrobat Reader\DC\AVGeneral
MUTANT_ALLOW_ANY = *
SECTION_ALLOW_ANY = *
You will find further information in the following document:
(Chapter 3 protected mode)
Current software versions are always compatible with all existing firmware versions. Once purchased devices are always supported by new versions of the software.
Conversely, current levels of hardware are expecting the latest software versions as well. The hardware (as well as the software) is always making progress. Of course new features new features sometimes also expect current software versions.
For example the models Sigma 1:26 (revision E) and Omega 1:35 (revision F) and newer.
These devices mandatorily need one of the following components that are available since 2011-10-25:
STPadCapt.ocx, STPadLib.dll or STPadLibNet.dll
Version 184.108.40.206 or newer
STPadJava.dll / libSTPadJava.so or STPadJava64.dll / libSTPadJava64.so
Version 220.127.116.11 or newer
Do you get the warning „At least one signature has problems.” after opening the signed document with Adobe Acrobat Reader?
© signotec GmbH Show in original size 6 KB - 240 x 41
A certificate has been used for signing, which is classified as untrustworthy by Adobe. Therefore the identity cannot be verified and you see this warning. This message is legally not a problem and the validity of the signature can still be verified. For a successful identity verification, please proceed as follows:
Right click on the signature > Show Signature Properties… > Show Signer’s Certificate… > Trust > Add to Trusted Certificates…
Please confirm all dialogs with OK and verify the signature again. Now you should get the message „Signed and all signatures are valid.”
© signotec GmbH Show in original size 6 KB - 229 x 41
Alternatively you have the option to buy a certificate from a certification authority and use it for signing. Certificates (identities) which are created from this authorities will be trusted by Adobe and the mentioned warning wil not show up.
Firstly, it should be noted that Citrix or the terminal server does not have the option to directly access native USB devices on the fat or thin client. Despite this, we offer a perfect solution to allow the signotec pads to be operated in such an environment:
- The Sigma or Omega pad with an external USB/Ethernet adapter. In the case you can access the pads via TCP/IP. The signature pads will be not connected to a PC or Thin-Client! You can access the signature pad from different PCs.
- The Sigma or Omega pad with an internal USB-to-serial converter. These devices can be connected to the thin client by USB. A virtual COM port is generated on the client, which is addressed as described: In the case of COM Port Mapping, the serial connection of the client (thin client or fat client) can be transparently switched to the terminal server. The drivers for the internal converter, for example, are part of the Linux operating system from kernel 2.4.20. The Windows drivers are Microsoft WHQL certified. You can download the drivers here. You will also find further information there.
The signotec signature pads with an internal USB-Serial-Converter ends with an FT like ST-BE105-2-FT100. More details you will find in the data sheets.
Precise instructions in English are available here for Citrix, Terminalserver and Remote Desktop.
signotec signature pads can be operated on IGEL ThinClients.
To be able to use the signature pad connected via USB in the session, there are two options available.
1. signotec virtualChannel driver
From the following IGEL ThinClient OS versions, the signotec VirtualChannel driver is already integrated and can be activated in the settings.
5.12.100 (V5 Release)
10.03.100 (V10 Release)
The signotec VirutalChannel driver can only be used for Citrix sessions.
2. signotec VCOM driver
As an alternative to the VirtualChannel and explicitly for use in RDP sessions, the signotec VCOM driver makes it possible to operate the signature pad as a virtual serial device and to pass it into the session via COM Port mapping.
Parallel operation is not possible because the VCOM driver permanently blocks a connected signature pad.
If both the VCOM driver and the virtual channel are activated, a connected signature pad can still be passed on to Citrix sessions, but not via the fast and robust virtual channel, but via the mapped VCOM port.
For thin clients, which are used purely for Citrix sessions, the VCOM driver should therefore be deactivated.