Frequently asked questions
Frequently asked questions
- 1. What is the crypto provider version?
- open the C:\Program Files\GammaTech\TumarCSP\lib\ folder;
- find the cptumar.dll file in the folder;
- right-click on the selected file and select the Version tab in the next window.
- How to run the TumarCSP Configurator?
- double-click on the TumarCSP Configurator icon located on the desktop; or
- select the menu item .
- How do I know what profiles are created?
- run the Configurator - see step 2;
- displaying the main Configurator window - the Profiles panel will display a list of existing profiles.
- How to determine the key presence in the profile?
- run the Configurator - see step 2;
- select the desired profile in the Profiles panel of the main Configurator window and click on it with the left mouse button;
- at the bottom of the window - in the Key list - the keys stored in the profile will be displayed, with additional information about each key.
- The keys are in the profile, but they are not displayed. Why?
This is possible if:
- incorrect profile settings (password, storage device parameters, container name) are indicated;
- no password for keys is indicated.
- How do I view/change the profile settings?
- run the Configurator - see step 2;
- select the desired profile in the Profiles panel of the main Configurator window and click on it with the right mouse button;
- select the Edit profile menu item in the context menu.
- How do I know if a license for a crypto provider is installed (valid)?
- run the Configurator - see step 2;
- the license name and its validity will be displayed in the title bar of the window;
- if the crypto provider does not have a license, a warning message will be displayed.
- How can I find out which crypto providers are installed in the system?
- start the registry editor ( );
- deploy the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Defaults\Provider;
- The subkeys appearing represent a list of installed crypto providers.
- How do I view the certificates stored in a container?
- run the Configurator - see step 2;
- select the desired profile in the Profiles panel of the main Configurator window and click on it with the left mouse button;
- at the bottom of the window - in the Key list - the keys stored in the profile will be displayed, with additional information about each key;
- double-click on the certificate icon in the line with the selected key;
- depending on the type of stored key information, either the certificate itself or the mmc console will be opened.
Note:- If the profile does not contain certificates, then the Key will be specified in the profile Key list in the Data type column;
- If the profile contains a user certificate, then the Key and certificate will be specified in the profile Key list in the Data type column;
- If the profile contains a user certificate and a CA certificate, then the Key and chain of certificates will be specified in the profile Key list in the Data type column.
- Where are the work protocols, requests, Configurator work reports stored?
The file with the last request sent to the CA/file with the last received response from the CA/log file of the cptumar.log Configurator is stored in the directory
- %AppData%\tumarCSP
The log file tumservice.log.txt of the TumService.exe service (TumSRV) is stored in the directory:
- %Temp%
The TumProcess.exe service log file:
- in the 32-bit OS the file tumprocess32.log.txt is stored in the directory – %Temp%
- in the 64-bit OS the files tumprocess32.log.txt and tumprocess64.log.txt are stored in the directory – %Temp%
- Where is cptumar.conf stored?
The configuration file is stored in in the file system: for catalogue C:\ProgramData\GammaTech\TumarCSP.
- Correcting the GetListReader error: SCardEstablishContext[-2146435043]
Cause - the SmartCard service is disabled.
Correction method:
-
Perform the following:
. -
Select the Smart Card service from the list.
-
Click on the Start the service link.
-
- Windows cannot verify the digital signature of this fileNote: Error may occur when working on operating systems: Windows Server (x64) 2008 R2/2012 R2/2016.
Cause - the operating system is not updated.
Correction method: Install operating system updates.