Difference between revisions of "MySQL - Initial Configuration"

From The TinkerNet Wiki
Jump to navigation Jump to search
(Created page with "'''tinker@doh:~$''' <code>sudo mysql_secure_installation</code> Securing the MySQL server deployment. Connecting to MySQL using a blank password. VALIDATE PASSWORD PLU...")
 
Line 12: Line 12:
 
  Press y|Y for Yes, any other key for No:  
 
  Press y|Y for Yes, any other key for No:  
  
<nowiki>********</nowiki>
+
'''''Probably should be Yes, but only if you are willing to fight with it over password rules...'''''
 
 
Probably should be Yes, but only if you are willing to fight with it over password rules...
 
 
 
<nowiki>********</nowiki>
 
  
 
  Please set the password for root here.
 
  Please set the password for root here.
Line 24: Line 20:
 
  Re-enter new password:  
 
  Re-enter new password:  
  
<nowiki>********</nowiki>
+
'''''This is where you choose a password for administering the database...'''''
 
 
This is where you choose a password for administering the database...
 
  
<nowiki>********</nowiki>
+
Whenever you need to sign into MySQL for administration, you'll sign in as root using this password
  
 
  By default, a MySQL installation has an anonymous user,
 
  By default, a MySQL installation has an anonymous user,
Line 39: Line 33:
 
  Remove anonymous users? (Press y|Y for Yes, any other key for No) :  
 
  Remove anonymous users? (Press y|Y for Yes, any other key for No) :  
  
<nowiki>********</nowiki>
+
'''''Say Yes...'''''
 
 
Say Yes...
 
  
<nowiki>********</nowiki>
+
(Who in heck wants an anonymous user in there database???)
  
 
  Success.
 
  Success.
Line 53: Line 45:
 
  Disallow root login remotely? (Press y|Y for Yes, any other key for No) :  
 
  Disallow root login remotely? (Press y|Y for Yes, any other key for No) :  
  
<nowiki>********</nowiki>
+
'''''Say no if you want to administer MySQL from, say, a script running on another machine.'''''
 
 
Say no if you want to administer MySQL from, say, a script running on another machine.
 
  
 
If your server is not accessible to the outside world for administrative stuff, this is safe to do.
 
If your server is not accessible to the outside world for administrative stuff, this is safe to do.
 
<nowiki>********</nowiki>
 
  
 
  ... skipping.
 
  ... skipping.
Line 69: Line 57:
 
  Remove test database and access to it? (Press y|Y for Yes, any other key for No) :  
 
  Remove test database and access to it? (Press y|Y for Yes, any other key for No) :  
  
<nowiki>********</nowiki>
+
'''''Just say Yes'''''
 
 
Just say Yes
 
  
<nowiki>********</nowiki>
+
(Don't think I've EVER used the test database...  EVER...)
  
 
  - Dropping test database...
 
  - Dropping test database...
Line 86: Line 72:
 
  Reload privilege tables now? (Press y|Y for Yes, any other key for No) :  
 
  Reload privilege tables now? (Press y|Y for Yes, any other key for No) :  
  
<nowiki>********</nowiki>
+
'''''Say yes...'''''
 
 
Say yes...  This is a silly question.
 
  
<nowiki>********</nowiki>
+
This is a silly question.
  
 
  Success.
 
  Success.

Revision as of 01:32, 26 June 2020

tinker@doh:~$ sudo mysql_secure_installation

Securing the MySQL server deployment.

Connecting to MySQL using a blank password.

VALIDATE PASSWORD PLUGIN can be used to test passwords
and improve security. It checks the strength of password
and allows the users to set only those passwords which are
secure enough. Would you like to setup VALIDATE PASSWORD plugin?

Press y|Y for Yes, any other key for No: 

Probably should be Yes, but only if you are willing to fight with it over password rules...

Please set the password for root here.

New password: 

Re-enter new password: 

This is where you choose a password for administering the database...

Whenever you need to sign into MySQL for administration, you'll sign in as root using this password

By default, a MySQL installation has an anonymous user,
allowing anyone to log into MySQL without having to have
a user account created for them. This is intended only for
testing, and to make the installation go a bit smoother.
You should remove them before moving into a production
environment.

Remove anonymous users? (Press y|Y for Yes, any other key for No) : 

Say Yes...

(Who in heck wants an anonymous user in there database???)

Success.

Normally, root should only be allowed to connect from
'localhost'. This ensures that someone cannot guess at
the root password from the network.

Disallow root login remotely? (Press y|Y for Yes, any other key for No) : 

Say no if you want to administer MySQL from, say, a script running on another machine.

If your server is not accessible to the outside world for administrative stuff, this is safe to do.

... skipping.
By default, MySQL comes with a database named 'test' that
anyone can access. This is also intended only for testing,
and should be removed before moving into a production
environment.

Remove test database and access to it? (Press y|Y for Yes, any other key for No) : 

Just say Yes

(Don't think I've EVER used the test database... EVER...)

- Dropping test database...
Success.

- Removing privileges on test database...
Success.

Reloading the privilege tables will ensure that all changes
made so far will take effect immediately.

Reload privilege tables now? (Press y|Y for Yes, any other key for No) : 

Say yes...

This is a silly question.

Success.

All done! 

tinker@doh:~$