Migrate Settings from Existing Configuration Files
A migration script is installed with Reflection for Secure IT, which you can use to migrate settings configured using any of the following products:
F-Secure UNIX clients and servers
The migration script is installed to:
The script examines your configuration files to determine if setting changes are required. If changes are needed, you are prompted to confirm that you want to apply these changes. After you confirm the migration, new configuration files are created with the required updates along with backups of your original files. All operations are detailed in the script’s output and log files. The log files document which settings have been migrated and which cannot be migrated. Log files are created in the same directory as the converted file and have names based on the converted filename (for example, sshd2_config_migration.log).
To migrate global configuration files
Note: When you run the migration script with no arguments, it migrates files located in the/etc/ssh2 directory. If /etc/ssh2/sshd2_config and /etc/ssh2/ssh2_config contain non-default settings, you are asked if you want to migrate these files. If these settings contain default values (which is the expected state after you uninstall the prior version and then install the current version), the script looks for the most recent backup files (for example *.rpmsave, *.save or *.backup) and asks if you want to migrate settings in the backup files.
To migrate a user configuration file
To migrate PKI settings
You can use the following procedure to migrate certificate settings if Reflection PKI Services Manager is installed on a computer that has Reflection for Secure IT 6.x or F-Secure configuration files.
Note: If the pki_config file in the destination folder already has a trust anchor configured, no migration occurs. This helps ensure that the migration won't overwrite modifications you have already configured.