Rocket Business Connect

Alert : Automatic Data Encryption can store data in clear text

Beginning at UniVerse release 10.3.4, new records written to an encrypted file which has a trigger will be stored in clear text.

This issue creates a security risk for your data and it is also possible that processes which access this file will not function correctly.

The root cause of this problem has been determined and a fix has been generated. The fix is scheduled to be available in the 10.3.x release planned for delivery by April 30, 2011.

At current 10.3 releases with the problem (10.3.4 thru 10.3.10), it is recommended that triggers are not used on encrypted files.

If you are currently using one of the affected releases and have a trigger on an encrypted file, the following procedure is recommended to handle the situation until the fix release is available.

• At the operating system level, make a backup copy of the encrypted file (i.e. cp filename filename.bak).
• Using the DECRYPT.FILE command, decrypt the data in the file.
• Using the DROP TRIGGER command, drop the trigger on the file.
• Using the ENCRYPT.FILE command, encrypt the data in the file.

If you have any questions on the above procedure or need more information on the problem, you can call U2 Support and reference the issue UNV-4909.