Linux version of 1.03 Compliance Test Tool|OPC Certification and Interoperability Testing|Forum|OPC Foundation

Hello Paul and Vincent, 

Thank you for your answers and suggestions. 

In the meantime, I had some progress. 

I had big issues running this tool on the 64-bit machine. I first thought that the problem is that I don’t have the needed 32-bit libraries and I installed some which were recommended on the web, like libc6-i386. But then, I realized that actually there was a problem with the certificate generator.

The certificate generator can be found under: /opt/opcfoundation/uactt/certificate_generator/

Two files are available: the shell file create_ctt_pki.sh and the configuration file openssl.cnf. As officially delivered, the shell script always crushes on the test “CTT Expired User Certificate – Trusted”. When I would deactivate that particular certificate-function, it would finish creating all the certificates. So, I knew that that certificate causes the problem but I didn’t know why. I saw that the .per file would get created, but the .txt file would get created in the TMPPKI folder, but the .txt.attr file not, only for that particular test. So the problem had to be somewhere in between. After further investigation, I realized that the PEM certificate is created but will not be converted to DER, and on top of that, the PEM certificate had the size of 0 kbytes (an empty file). After further investigation, I found out that there is no definition for “CERTNO”, only for CERTN and CERTO (for the 0= option), and that caused the generator to crush. Unfortunately, I was unable to post images, I wanted to show you exactly where it is, but if you search for “CERTNO” in the shell script file, there is only one place and that is this one. The same warning and problem appeared for the 32 bit version, but the generator skipped the warning.

After fixing it, everything functioned. I could copy the folder with the certificates in my Project and use them.

NOTE: it can be, that the PKI folder is locked and unusable because it belongs to root. In order to change the permission level use: chmod a+rwx <FOLDER_NAME>

I hope that my detailed investigation will help you be able to correct this small typo and be ready for the 64 version faster

Or at least, I hope it will be helpful for people who want to run the tool on 64 bit linux.

Many greetings, 
Elena Petrevska