Database encryption: hcidbcrypt

The error database is in a SQLite database, where you can edit, resend, and search the error database. A user interface similar to SMAT is available to manage the database.

This command is provided for users to change the error and internal database passwords.

hcidbcrypt {-e|-I} [-d] [-p password] [-q]

Both the error and internal database are supported for encrypting/decrypting with a user-defined password.

  • -e specifies encryption/decryption of the error database.
  • -I specifies encryption/decryption of the internal databases. For example, the recovery database..
  • -d specifies to do decryption, when it is given; otherwise, encryption.
  • -p password specifies the encryption key.

    If this option is not specified, then the default encryption key is used.

  • -q indicates quiet, or no output except errors.

To change the error database password:

  • Decrypt the error database or internal database using the old password:
    hcidbcrypt {-e|-I} [-d] [-p] oldpassword [-q]
  • Encrypt the error database or internal database with the new password:
    hcidbcrypt {-e|-I} [-d] [-p] newpassword [-q]

If the -p option is not used in the command, then the engine uses the default password to encrypt/decrypt the database.

siteSecurityInfo keys

These keys in siteSecurityInfo are updated based on the encryption/decryption option:

  • dbencryption

    The default is 1: Raima databases are encrypted.

  • internaldbkey

    The default is "": Use the default Raima database key for encryption.

  • errordbencryption

    The default is 1: Error database is encrypted.

  • errordbkey

    The default is "": Use the default error database key for encryption.

siteSecurityInfo is encrypted. The keys that are saved in this file are plain text.