All data files and transaction logs are encrypted before writing to disk. There is support for encrypting network traffic using SSL (client-server as well as replication.) Encryption support is for data at-rest only i.e. it protects systems from attacker with access to physical media. Encryption does not protect against attacker with access to system or process memory. Mechanics for at-rest encryption is similar to Berkeley DB: AES-128 and 16-byte initialization vector, with the following changes:
The encrypted files are endian-agnostic
Comdb2 uses OpenSSL for encryption routines
The encrypted data is checksummed using crc32c
Initialization vector is generated using RAND_bytes()
Comdb2’s Berkeley DB environment is always opened with DB_PRIVATE flag
Encryption can only be enabled at database creation time. To modify encryption settings (change password, enable or disable encryption) requires dump and load of existing data. To enable encryption add following to the lrl file:
There are no key management facilities at this point and it is up to the admin to properly secure the password file.