Open Source Software

This software includes a number of Open Source components that were published under different licenses. You can find a list of all components and licenses here.

System Requirements

Hardware

• Processor
  x86 compatible CPU, min. 1 GHz
• RAM
  at least 1 GB, 2 GB recommended.
  Provize® Classic WebView requires approx. 200 MB free RAM.
  For every open window, Provize® Classic WebView requires an additional 500 MB RAM.
• Disk space
  1 GB free.
• Monitor resolution
  at least 1024x768 pixels.
  

Operating system

• Windows 7 (64 Bit)
• Windows 8.1 (64 Bit)
• Windows 10 Version: 1803 (64 Bit)
• Windows Server 2019
• Windows 11
• PC Linux (64 Bit: Kernel 3.10, libc 6):
  Debian 10
  Red Hat 8
  
  Note: Redhat 7 and debian 9 are no longer supported, because they do not contain the glibc-2.27 library. To use Provize® Classic WebView 01.1.01, either update your Linux Operating System or install the glibc-2.27 library.
  

Starting

File Check

• For Windows users, the Windows utility certutil can be used to calculate the sha256 hash. In the cmd window, navigate to the file location then enter the following command:
  CertUtil -hashfile path\file_name.ext SHA256 (Example: CertUtil -hashfile C:\Download\Provize® Classic WebView.zip SHA256)
• For Linux users, verify that you have administrator rights then enter the following command:
  sha256sum path/file_name.ext (Example: sha256sum /provize-classic-webview.zip)

Deploying to Provize® Suite under Windows

• For Provize® Suite 01.9.01 (or later) to be able to access Provize® Classic WebView, extract the archive provize-classic-webview01101_windows.zip into your Local Disk (C:) directory: \Users\Username\AppData\Roaming\provize-suite\plugins\webview.
• Since Provize® Suite 01.11.01 you can import Provize® Classic WebView as a plugin using a dedicated option in the menu.

Verifying the Fingerprint of a Device Certificate

• If Provize® Classic WebView does not have an HTTPS certificate fingerprint on record for a device, then Provize® Classic WebView displays the "Confirm HTTPS Certificate" dialog. The dialog contains the fingerprint of the HTTPS certificate. Provize® Classic WebView also displays the "Confirm Applet Signature Certificate" dialog when a fingerprint for an applet signing certificate is not on record.
• ***
• Important: To help prevent a man-in-the-middle attack, verify that the dialog contains the correct fingerprint.
• ***
• If you do not know the fingerprint of the HTTPS/Applet Signature certificate, please ask your network administrator.
• After the network administrator gets the fingerprint of the certificate, the network administrator uses a secure channel to send the fingerprint to the remote client. The remote client compares the fingerprint received from the network administrator to the fingerprint in the dialog. To help you verify the fingerprint, Provize® Classic WebView lets you paste the fingerprint in the "Fingerprint to verify" field.
• If Provize® Classic WebView does not display the "Confirm HTTPS/Applet Signature Certificate" dialogs, then Provize® Classic WebView accepted the fingerprint permanently in a previous session.
  To display the dialogs again, perform the following steps:
  • Close the GUI of the device.
  • For the device's HTTPS Certificate:
    • Open the <Installation directory>/ssl_known_hosts text file.
    • Remove the line that contains the IP address and fingerprint of the HTTPS Certificate.
  • For the vendor's Applet Certificate:
    • Open the <Installation directory>/known_applet_signatures text file.
    • Remove the line that contains the fingerprint of the Applet Certificate and the vendor.
  • Start the GUI of the device again.

SHA1/TLSv1 and TLSv1.1 algorithm handling

• The SHA1/TLSv1 and TLSv1.1 algorithms are deprecated and have been succeeded by newer algorithms. Devices or servers with older software sometimes still use the deprecated algorithms. Therefore Provize® Classic WebView supports these deprecated algorithms, if the usage of the newer algorithms is not possible.
• To no longer support the usage of the deprecated algorithms and help make Provize® Classic WebView secure, perform the following steps:
  • Using a text editor, save a text file as C:\Users\Username\AppData\Roaming\provize-suite\plugins\webview\security.properties
  • Enter the following text into the security.properties file:
    
    • sha.reenableUnsecureSHA_Algorithms=false
    • tls_v10.client.activate=false
    • tls_v11.client.activate=false
  • Save the security.properties file.