The MySQL Keyring | License | GPL | | Implementation_name | component_keyring_file | | Version | 1.0 | | Component_status | Active | | Data_file | /usr/local/mysql/keyring/component_keyring_file | | Read_only | No | +---------------------+-------------------------------------------------+ 1447 Command-Line Format --keyring-migration- password[=password] Type String Command-Line Format --keyring-migration-host=host_name Type String Default Value localhost Command-Line Format --keyring-migration- destination=plugin_name Type String A  Component_status  value of  Active  indicates that the component initialized successfully. If the component loaded but failed to initialize, the value is  Disabled . MySQL supports the following keyring-related command-line options: The destination keyring plugin for key migration. See Section 6.4.4.13, “Migrating Keys Between Keyring Keystores” . The option value interpretation depends on whether  --keyring-migration-to- component  is specified: --keyring-migration-source  and  --keyring-migration- destination  are mandatory for all keyring migration operations. The source and destination plugins must differ, and the migration server must support both plugins. The host location of the running server that is currently using one of the key migration keystores. See Section 6.4.4.13, “Migrating Keys Between Keyring Keystores” . Migration always occurs on the local host, so the option always specifies a value for connecting to a local server, such as  localhost , 127.0.0.1 ,  ::1 , or the local host IP address or host name. • --keyring-migration-password[= password ] • --keyring-migration-host= host_name • If yes, the option value is a keyring component, specified as the component library name in the plugin directory, including any platform-specific extension such as  .so  or  .dll . •If no, the option value is a keyring plugin, interpreted the same way as for  --keyring-migration- source . • --keyring-migration-destination= plugin 6.4.4.17 Keyring Command Options Note