Previous Topic

Next Topic

LOG_ENCRYPT Option Now Correctly Supported with Advanced Encryption

c-treeACE failed to start with a log incompatibility error LFRM_ERR (666) when both the log encryption option LOG_ENCRYPT and advanced encryption (ADVANCED_ENCRYPTION YES) options were in effect. c-treeACE would even fail to start in a directory with no existing transaction log files.

Comprehensive checks during c-treeACE startup are now done to ensure that log encryption settings are appropriate for the type of encryption for existing transaction logs. When an incompatibility is found, c-treeACE startup fails with an error message in CTSTATUS.FCS indicating which options must be changed to access the transaction log files.

The table below shows the expected results for the possible combinations of Log Encryption and Advanced Encryption for each possible transaction log encryption type used by an existing log file.

Log
Encryption
Option

Advanced
Encryption
Option

Log
Encryption
Type

Expected result

N

N

None

OK

N

Y

None

OK

Y

N

None

OK, new logs encrypted with CAMO encryption

Y

Y

None

OK, new logs encrypted with advanced encryption

N

N

CAMO

Error: Enable log encryption to proceed

N

Y

CAMO

Error: Enable log encryption and disable advanced encryption to proceed

Y

N

CAMO

OK

Y

Y

CAMO

Error: Disable advanced encryption to proceed

N

N

Advanced

Error: Enable log encryption and advanced encryption to proceed

N

Y

Advanced

Error: Enable log encryption to proceed

Y

N

Advanced

Error: Enable advanced encryption to proceed

Y

Y

Advanced

OK