Frequently Asked Questions - General (installing, licensing ...)

intarsys products are not affected because

1. only the intarsys product SLcs gears spring is used
2. SLcs gears is operated with Java 8
3. SLcs gears does not use spring-webmvc or spring webflux.

intarsys products are not affected by the security problem!

You can find the following intarsys products in the supported versions continue to operate without changes:

• PDF / A Live!
• Sign Live! CC
• Sign Live! CC DATEV edition
• Sign Live! CC SPARKASSEN edition
• Sign Live! cloud suite bridge
• Sign Live! cloud suite gears
• Sign Live! cloud suite SDK

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.

Product-specific explanations

• In Sign Live! cloud suite gears Third-party products used up to version 8.7 are based on the critical Log4j version 2.14, but in the context of gears the dangerous library log4j-core- *. jar neither delivered nor used. There is therefore no potential risk.
• With Sign Live! CC delivered Exampleimplementations (SDK / JMS) use Log4j version 1.x. These are only activated by calling the command line on the system and are also required a special Log4j configuration. They are therefore not considered to be a potential hazard.

Further safety information on the required basic components

tom cat 9 does not use Log4j in its basic configuration without standard and other web apps.

General safety information on the required basic components

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 + .

Further background information

• heise.de December 10.12.2021, XNUMX
• heise.de December 13.12.2021, XNUMX

In the following, you will learn how to set up a remote connection to a JVM for can build up.
Security aspects are deliberately not taken into account. For this and more in-depth information, please refer to the linked information.

1. JVM the vorbereit
   Digression for SLCC/PDFA/SLcsbridge:
   For the use of JMX on the client side (where the intarsys product is operated) a complete JRE thats it!
   The above products are offered at reduced prices JREs shipped. Therefore, it must first be ensured that the intarsys product comes with a complete JRE starts.
   You will find information on this in this FAQ SLCC with my" JVM start.

   Configuration of the JVM for remote access
   For remote access to the JVM a port must be defined and, for the sake of simplicity, security mechanisms must be switched off.
   Add the following definitions to your Java configuration (any free port can be used as a port)

   -Dcom.sun.management.jmxremote.port = 50999 -Dcom.sun.management.jmxremote.authenticate = false -Dcom.sun.management.jmxremote.ssl = false

   For z. B. SLCC put this data in the file C: \ Program Files \ Sign Live CC 7.1.7 \ bin \ SignLiveCC.exe.vmoptions and restart the application.
   your JVM is now available for remote access via JMX configured.
    

2. Connection to JVM build with jconsole
   Start the Java tool jconsole on the client.
   You can find it in your Java installation (JDK) z. E.g. in the path C: \ Program Files \ Java \ zulu11.48.21-ca-jdk11.0.11-win_x64 \ bin \ jconsole.exe

   Select the one to be monitored JVM via the defined connection data:

   

   acknowledge the warning

   

   ... and you get access to the JVM. After switching to the tab MBeans do you read e.g. B. the current license status:

   

More information

1. The version of the client JDKs is independent of the one used in the intarsys product.
   It has to be JDK .
2. When accessing from localhost, there is no need to define a port or switch off security. 

More detailed information

1. https://docs.oracle.com/javase/1.5.0/docs/guide/management/index.html
   therein
   • https://docs.oracle.com/javase/1.5.0/docs/guide/management/jconsole.html
   • https://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#re…
2. https://www.oracle.com/technical-resources/articles/javase/jmx.html

You can verify the integrity of the downloaded software with a checksum file before installing it.
To do this, download the corresponding text file with the extension ".digest.txt" or ".md5".

This text file contains one or more checksums for the The software installation file available in the same download area.

There are various test programs that can determine a checksum from the downloaded software.
This checksum must then be compared with the checksum in the text file.
If the checksums are the same, the software you downloaded is identical to the software that we officially made available.

Possible test programs are, for example:

• md5summer.exe for Windows
• md5sum under Linux
• sha1sum under Linux
• sha256sum on Linux
• md5 under MacOS
• CertUtil -hashfile under Windows

The checksums we determine are based on the following procedure:

• MD5

Note: If you have already installed the same version or a previous version of the application, or if you install a patch:

• Quit the application (preferably via the system tray) if it has started.
• If you have configured the software as a Windows service, stop the Windows service.
• Please also note the  Release Notes.

How to install the software on a Microsoft Windows system:

1. Download the installation file with the extension “.exe”.
2. If you would like to check the integrity of the installation medium using a checksum file before installation, download the corresponding text file with the extension ".digest.txt" or ".md5". The procedure for testing is a separate one FAQ described. This check is not absolutely necessary for correct installation.
3. Run the downloaded setup file.
4. Start the installed application if it does not start automatically.
5. If necessary, carry out the online activation.

A Tutorial with step-by-step instructions on how to download the software, install it, and activate the product    here .

How to install Sign Live! CC on an Apple MacOS system:

1. Download the file with the extension “.dmg”.
2. You can check the integrity of the installation medium before installation using a checksum file. To do this, download the corresponding text file with the extension “.digest.txt” or “.md5”. The procedure for testing is a separate one FAQ described. This check is not absolutely necessary for correct installation.
3. If you have already installed the same version or a previous version of the application:
   • Quit the application if it has started.
4. After double-clicking on the Mg File (the disk image) appears in the Finder as a virtual drive.
5. Drag the application icon into the application directory.
6. Check your installation.
7. Start the installed application.

How to install a patch to an existing version:

1. Download the file with the extension “.dmg”.
2. You can check the integrity of the installation medium before installation using a checksum file. To do this, download the corresponding text file with the extension “.digest.txt” or “.md5”. The procedure for testing is a separate one FAQ described.
3. Please make sure that the application “Sign Live! CC“Was started once before the patch was installed and then closed again or close the application if it was started.
4. After double-clicking on the disk image, the SLCC Patcher app.
5. Run SLCC Patcher App with a double click.
6. Check the version number displayed and confirm that the patch should be applied.
7. Select the appropriate installation directory for Sign Live! CC and start the installation.
8. A success message appears after the patch has been installed.
9. Check your installation.
10. Start the installed application.

A Tutorial with step-by-step instructions on how to download the software, install it, and activate the product   here .

How to install the software on a Linux system:

1. Download the file with the extension “.tar.gz”.
2. You can use a checksum file to verify the integrity of the installation media prior to installation. To do this, download the corresponding text file with the extension “.digest.txt” or “md5”. The procedure for the test is in a separate FAQ described. This check is not absolutely necessary for correct installation.
3. If you have already installed the application in a previous version or if you are installing a patch:
   • Quit the application if it has started.
   • If you have configured the software as a Linux service, stop the Linux service.
4. Unzip the downloaded file as follows, using the file name of the downloaded file plus the version number as the name for the installation directory:
   tar -xf signlivecc_*.tar.gz -C /opt/signlivecc-7.1.8/
5. Check your installation.
6. Start the installed application.

• Note:
  Also extract an update into a new directory in order to avoid that the installation contains contents from different versions. Specific adaptations must be carried out again or adopted after the installation.
• Note:
  The file name of the downloaded file differs depending on the product. For the example in point 4 is the product Sign Live! CC .
• Note:
  The SLCC-Profile directorySLCC_PROFILE> for user operation is configured inSLCC_INSTALL>/config/stage.config
  (usually under /home/ /signlivecc-${stage.major}.${stage.minor})
  that for the service is configured inSLCC_INSTALL>/config/service.config
  (usually /var/opt/signlivecc-${stage.major}.${stage.minor}).
• Note:
  License files are to be stored inSLCC_INSTALL>/licenses orSLCC_PROFILE>/licenses.

Our products read the fonts from the standard directory. On Windows this is C: \ Windows \ Fonts. In the user view, not only the fonts from this directory are displayed, but also the fonts from the user directory. This can only be seen when the properties of a font are displayed.

Copied If you put a font in the directory C: \ Windows \ Fonts, it will be displayed there, but is de facto in the user directory. Our software does not access the user directory by default, so the font is not available even though you see it in the supposedly correct place.

Solution:

• Install The font instead of copying it. Use You to this context menu (right mouse button) and choose "Install for everyone". This will put the font in the correct directory.