MySQL supports the following keyring-related command-line options:
--keyring-migration-destination=pluginCommand-Line Format --keyring-migration-destination=plugin_nameIntroduced 5.7.21 Type String The destination keyring plugin for key migration. See Section 6.4.7, “Migrating Keys Between Keyring Keystores”. The format and interpretation of the option value is the same as described for the
--keyring-migration-sourceoption.Note--keyring-migration-sourceand--keyring-migration-destinationare mandatory for all keyring migration operations. The source and destination plugins must differ, and the migration server must support both plugins.--keyring-migration-host=host_nameCommand-Line Format --keyring-migration-host=host_nameIntroduced 5.7.21 Type String Default Value localhostThe host location of the running server that is currently using one of the key migration keystores. See Section 6.4.7, “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]Command-Line Format --keyring-migration-password[=password]Introduced 5.7.21 Type String The password of the MySQL account used for connecting to the running server that is currently using one of the key migration keystores. See Section 6.4.7, “Migrating Keys Between Keyring Keystores”.
The password value is optional. If not given, the server prompts for one. If given, there must be no space between
--keyring-migration-password=and the password following it. If no password option is specified, the default is to send no password.Specifying a password on the command line should be considered insecure. See Section 2.2.1, “End-User Guidelines for Password Security”. You can use an option file to avoid giving the password on the command line. In this case, the file should have a restrictive mode and be accessible only to the account used to run the migration server.
--keyring-migration-port=port_numCommand-Line Format --keyring-migration-port=port_numIntroduced 5.7.21 Type Numeric Default Value 3306For TCP/IP connections, the port number for connecting to the running server that is currently using one of the key migration keystores. See Section 6.4.7, “Migrating Keys Between Keyring Keystores”.
--keyring-migration-socket=pathCommand-Line Format --keyring-migration-socket={file_name|pipe_name}Introduced 5.7.21 Type String For Unix socket file or Windows named pipe connections, the socket file or named pipe for connecting to the running server that is currently using one of the key migration keystores. See Section 6.4.7, “Migrating Keys Between Keyring Keystores”.
--keyring-migration-source=pluginCommand-Line Format --keyring-migration-source=plugin_nameIntroduced 5.7.21 Type String The source keyring plugin for key migration. See Section 6.4.7, “Migrating Keys Between Keyring Keystores”.
The option value is similar to that for
--plugin-load, except that only one plugin library can be specified. The value is given asplugin_libraryorname=plugin_library, whereplugin_libraryis the name of a library file that contains plugin code, andnameis the name of a plugin to load. If a plugin library is named without any preceding plugin name, the server loads all plugins in the library. With a preceding plugin name, the server loads only the named plugin from the libary. The server looks for plugin library files in the directory named by theplugin_dirsystem variable.Note--keyring-migration-sourceand--keyring-migration-destinationare mandatory for all keyring migration operations. The source and destination plugins must differ, and the migration server must support both plugins.--keyring-migration-user=user_nameCommand-Line Format --keyring-migration-user=user_nameIntroduced 5.7.21 Type String The user name of the MySQL account used for connecting to the running server that is currently using one of the key migration keystores. See Section 6.4.7, “Migrating Keys Between Keyring Keystores”.