After using a batch insert to add records to a file that uses AES encryption, in rare cases reading the records failed with error 160 because the records were not decrypted properly.
A second way to encounter this issue was by changing c-tree's page size after writing the data. If a different cache page size was used when reading AES-encrypted data than when the data was written, the data file contents would not decrypt properly.
The logic has been corrected and a new version of the AES cipher has been introduced to preserve the ability to read files that were created using the AES cipher prior to this revision.
When using Advanced Encryption, FAIRCOM.FCS is encrypted using AES. Older versions of this file can be read by the updated logic.
During this testing, the following improvements were made to the ctscmp utility: