MYSQL_SECURE_INSTALLATION(1) | MySQL Database System | MYSQL_SECURE_INSTALLATION(1) |
NAME¶
mysql_secure_installation - improve MySQL installation security
SYNOPSIS¶
mysql_secure_installation
DESCRIPTION¶
This program enables you to improve the security of your MySQL installation in the following ways:
mysql_secure_installation helps you implement security recommendations similar to those described at Section 2.10.4, “Securing the Initial MySQL Account”.
Normal usage is to connect to the local MySQL server; invoke mysql_secure_installation without arguments:
shell> mysql_secure_installation
When executed, mysql_secure_installation prompts you to determine which actions to perform.
The validate_password plugin can be used for password strength checking. If the plugin is not installed, mysql_secure_installation prompts the user whether to install it. Any passwords entered later are checked using the plugin if it is enabled.
Most of the usual MySQL client options such as --host and --port can be used on the command line and in option files. For example, to connect to the local server over IPv6 using port 3307, use this command:
shell> mysql_secure_installation --host=::1 --port=3307
mysql_secure_installation supports the following options, which can be specified on the command line or in the [mysql_secure_installation] and [client] groups of an option file. For information about option files used by MySQL programs, see Section 4.2.6, “Using Option Files”.
Display a help message and exit.
Read this option file after the global option file but (on Unix) before the user option file. If the file does not exist or is otherwise inaccessible, an error occurs. file_name is interpreted relative to the current directory if given as a relative path name rather than a full path name.
For additional information about this and other option-file options, see Section 4.2.7, “Command-Line Options that Affect Option-File Handling”.
Use only the given option file. If the file does not exist or is otherwise inaccessible, an error occurs. file_name is interpreted relative to the current directory if given as a relative path name rather than a full path name.
For additional information about this and other option-file options, see Section 4.2.7, “Command-Line Options that Affect Option-File Handling”.
Read not only the usual option groups, but also groups with the usual names and a suffix of str. For example, mysql_secure_installation normally reads the [client] and [mysql_secure_installation] groups. If the --defaults-group-suffix=_other option is given, mysql_secure_installation also reads the [client_other] and [mysql_secure_installation_other] groups.
For additional information about this and other option-file options, see Section 4.2.7, “Command-Line Options that Affect Option-File Handling”.
Connect to the MySQL server on the given host.
Do not read any option files. If program startup fails due to reading unknown options from an option file, --no-defaults can be used to prevent them from being read.
The exception is that the .mylogin.cnf file, if it exists, is read in all cases. This permits passwords to be specified in a safer way than on the command line even when --no-defaults is used. (.mylogin.cnf is created by the mysql_config_editor utility. See mysql_config_editor(1).)
For additional information about this and other option-file options, see Section 4.2.7, “Command-Line Options that Affect Option-File Handling”.
This option is accepted but ignored. Whether or not this option is used, mysql_secure_installation always prompts the user for a password.
The TCP/IP port number to use for the connection.
Print the program name and all options that it gets from option files.
For additional information about this and other option-file options, see Section 4.2.7, “Command-Line Options that Affect Option-File Handling”.
The connection protocol to use for connecting to the server. It is useful when the other connection parameters normally would cause a protocol to be used other than the one you want. For details on the permissible values, see Section 4.2.2, “Connecting to the MySQL Server”.
For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
Options that begin with --ssl specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates. See Section 6.3.2, “Command Options for Encrypted Connections”.
The protocols the client permits for encrypted connections. The value is a list of one or more comma-separated protocol names. The protocols that can be named for this option depend on the SSL library used to compile MySQL. For details, see Section 6.3.6, “Encrypted Connection Protocols and Ciphers”.
This option was added in MySQL 5.7.10.
Execute noninteractively. This option can be used for unattended installation operations.
The MySQL user name to use when connecting to the server.
COPYRIGHT¶
Copyright © 1997, 2019, Oracle and/or its affiliates. All rights reserved.
This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.
SEE ALSO¶
For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/.
AUTHOR¶
Oracle Corporation (http://dev.mysql.com/).
04/12/2019 | MySQL 5.7 |