Fortinet white logo
Fortinet white logo

FortiGate cannot restore configuration file after private-data-encryption is re-enabled

FortiGate cannot restore configuration file after private-data-encryption is re-enabled

In a new enhancement, enabling private-data-encryption will utilize a randomly generated private key. Therefore, FortiGate cannot restore the configuration file in the following sequence:

  1. private-data-encryption enabled with random key, and configuration is backed up.

  2. private-data-encryption disabled.

  3. private-data-encryption enabled again, with new random key.

  4. Restore configuration file in step 1.

When disabling private-data-encryption, a warning in the CLI will be displayed:

This operation will restore system default data encryption key!
Previous config files encrypted with the private key cannot be restored after this operation!
Do you want to continue? (y/n)y

FortiGate cannot restore configuration file after private-data-encryption is re-enabled

FortiGate cannot restore configuration file after private-data-encryption is re-enabled

In a new enhancement, enabling private-data-encryption will utilize a randomly generated private key. Therefore, FortiGate cannot restore the configuration file in the following sequence:

  1. private-data-encryption enabled with random key, and configuration is backed up.

  2. private-data-encryption disabled.

  3. private-data-encryption enabled again, with new random key.

  4. Restore configuration file in step 1.

When disabling private-data-encryption, a warning in the CLI will be displayed:

This operation will restore system default data encryption key!
Previous config files encrypted with the private key cannot be restored after this operation!
Do you want to continue? (y/n)y