Skip to main content

Patch 10.4.02-026

Downloads

Product availability Matrix (PAM)
Downloads of this patch are available from the Rocket Customer Support Portal.
Further explanation can be found here.

Currencies

  • ProcScript functions $encode and $decode have been updated for improved security and performance.

Fixes

UNI-33041A long running process may end up in a deadlock when using Sentinel licenses.
UNI-19262Object name logged with IOPRINT=128 not always correct
UNI-2312Function $decode: crash can occur when decoding RSA encrypted data fails



UNI-33041  -  A long running process may end up in a deadlock when using Sentinel licenses.

Solution available in patch(es):      10.4.02-026

Description:

The deadlock occurs when the Sentinel client library tries to refresh the checked out licenses and Uniface has just locked a mutex.

Environment:

+Uniface: Version 10.4.02
+Operating System: Linux, Solaris, AIX
+Database: DBMS independent

Workaround:

The only workaround is to use a DLM license instead of a Sentinel one.

Notes:

When you use Sentinel version 9.6 or 9.8: this problem has been solved.
When you use Sentinel version 10: this problem has been solved for Linux and Solaris platforms. A solution for AIX is pending.

Back to top



UNI-19262  -  Object name logged with IOPRINT=128 not always correct

Solution available in patch(es):      10.4.02-026

Description:

When using IOPRINT (I/O Message Levels) 128 then all calls to global objects and descriptors are logged in the message frame or log. The name logged object name is hereby not always correct. Instead of showing the name of the object that is actually loaded the profile is shown.

Consider the following scenario:

$variation is set to the library TEST1
The IDE is started with IOPRINT=128 (e.g. using the command line option /pri=128)

In the log file or message frame the following messages should be visible:

Object size=0000032 msg/u_busy@test1@usa.msg
Object size=0001800 ktt/mswinx@test1.ktt

This somehow implies that both objects have been found in the library TEST1, but this is not the case. The objects in question do not exist in the library TEST1 and where instead loaded from the USYS library. The messages in the log or message frame therefore should say the following:

Object size=0000032 msg/u_busy@usys@usa.msg
Object size=0001800 ktt/mswinx@usys.ktt

Environment:

+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent

Workaround:

None

Notes:

This problem is solved.

Back to top



UNI-2312  -  Function $decode: crash can occur when decoding RSA encrypted data fails

Solution available in patch(es):      10.4.02-026

Description:

When a general error is occurring during the decoding of RSA encrypted data ($decode returns $procerror -1791) then this can cause a crash (heap corruption).

Consider the following scenario:

; Load keys
fileload "myPrivateKey.pem", vMyPrivateKey
; Decrypt the data
plaintext = $decode("RSAES_OAEP_SHA512", "xxx", vMyPrivateKey)

> Result: Uniface is crashing (when executing the $decode instruction) because of a Heap Corruption

Environment:

+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent

Workaround:

None

Notes:

This problem is solved.

Back to top



Be the first to reply!
Terms & ConditionsAccessibility statement