<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SQL commands for a fresh install</title>
	<atom:link href="http://themattreid.com/wordpress/2008/02/19/sql-commands-for-a-fresh-install/feed/" rel="self" type="application/rss+xml" />
	<link>http://themattreid.com/wordpress/2008/02/19/sql-commands-for-a-fresh-install/</link>
	<description>MySQL DBA &#124; Linux&#039;er</description>
	<lastBuildDate>Thu, 09 Sep 2010 17:40:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: sql command for changing password</title>
		<link>http://themattreid.com/wordpress/2008/02/19/sql-commands-for-a-fresh-install/comment-page-1/#comment-17</link>
		<dc:creator>sql command for changing password</dc:creator>
		<pubDate>Thu, 15 May 2008 22:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://themattreid.com/wordpress/?p=44#comment-17</guid>
		<description>[...] database installation. ... cannot be created without a password: NO_AUTO_CREATE_USER sql MODE. ...http://themattreid.com/wordpress/?p=44SQL Command and Function Reference - DBMaker Online / ManualsFor security reasons, users other than [...]</description>
		<content:encoded><![CDATA[<p>[...] database installation. &#8230; cannot be created without a password: NO_AUTO_CREATE_USER sql MODE. &#8230;http://themattreid.com/wordpress/?p=44SQL Command and Function Reference &#8211; DBMaker Online / ManualsFor security reasons, users other than [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: flupps</title>
		<link>http://themattreid.com/wordpress/2008/02/19/sql-commands-for-a-fresh-install/comment-page-1/#comment-6</link>
		<dc:creator>flupps</dc:creator>
		<pubDate>Wed, 20 Feb 2008 10:35:02 +0000</pubDate>
		<guid isPermaLink="false">http://themattreid.com/wordpress/?p=44#comment-6</guid>
		<description>The first steps will be covered by &quot;mysql_secure_installation&quot; on Unix systems, and on Windows the installer will take care of this for you...

flupps@flupps:~$ mysql_secure_installation 




NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!


In order to log into MySQL to secure it, we&#039;ll need the current
password for the root user.  If you&#039;ve just installed MySQL, and
you haven&#039;t set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none): 
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.

Set root password? [Y/n] 
New password: 
Re-enter new password: 
Password updated successfully!
Reloading privilege tables..
 ... Success!


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? [Y/n] 
 ... Success!

Normally, root should only be allowed to connect from &#039;localhost&#039;.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] 
 ... Success!

By default, MySQL comes with a database named &#039;test&#039; 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? [Y/n] 
 - 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? [Y/n] 
 ... Success!

Cleaning up...



All done!  If you&#039;ve completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!


flupps@flupps:~$</description>
		<content:encoded><![CDATA[<p>The first steps will be covered by &#8220;mysql_secure_installation&#8221; on Unix systems, and on Windows the installer will take care of this for you&#8230;</p>
<p>flupps@flupps:~$ mysql_secure_installation </p>
<p>NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL<br />
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!</p>
<p>In order to log into MySQL to secure it, we&#8217;ll need the current<br />
password for the root user.  If you&#8217;ve just installed MySQL, and<br />
you haven&#8217;t set the root password yet, the password will be blank,<br />
so you should just press enter here.</p>
<p>Enter current password for root (enter for none):<br />
OK, successfully used password, moving on&#8230;</p>
<p>Setting the root password ensures that nobody can log into the MySQL<br />
root user without the proper authorisation.</p>
<p>Set root password? [Y/n]<br />
New password:<br />
Re-enter new password:<br />
Password updated successfully!<br />
Reloading privilege tables..<br />
 &#8230; Success!</p>
<p>By default, a MySQL installation has an anonymous user, allowing anyone<br />
to log into MySQL without having to have a user account created for<br />
them.  This is intended only for testing, and to make the installation<br />
go a bit smoother.  You should remove them before moving into a<br />
production environment.</p>
<p>Remove anonymous users? [Y/n]<br />
 &#8230; Success!</p>
<p>Normally, root should only be allowed to connect from &#8216;localhost&#8217;.  This<br />
ensures that someone cannot guess at the root password from the network.</p>
<p>Disallow root login remotely? [Y/n]<br />
 &#8230; Success!</p>
<p>By default, MySQL comes with a database named &#8216;test&#8217; that anyone can<br />
access.  This is also intended only for testing, and should be removed<br />
before moving into a production environment.</p>
<p>Remove test database and access to it? [Y/n]<br />
 &#8211; Dropping test database&#8230;<br />
 &#8230; Success!<br />
 &#8211; Removing privileges on test database&#8230;<br />
 &#8230; Success!</p>
<p>Reloading the privilege tables will ensure that all changes made so far<br />
will take effect immediately.</p>
<p>Reload privilege tables now? [Y/n]<br />
 &#8230; Success!</p>
<p>Cleaning up&#8230;</p>
<p>All done!  If you&#8217;ve completed all of the above steps, your MySQL<br />
installation should now be secure.</p>
<p>Thanks for using MySQL!</p>
<p>flupps@flupps:~$</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arjen</title>
		<link>http://themattreid.com/wordpress/2008/02/19/sql-commands-for-a-fresh-install/comment-page-1/#comment-5</link>
		<dc:creator>arjen</dc:creator>
		<pubDate>Wed, 20 Feb 2008 04:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://themattreid.com/wordpress/?p=44#comment-5</guid>
		<description>Have you looked at the mysql_secure_installation script?
It does the removing of the anon user, setting up root pwd, etc...
Easy!</description>
		<content:encoded><![CDATA[<p>Have you looked at the mysql_secure_installation script?<br />
It does the removing of the anon user, setting up root pwd, etc&#8230;<br />
Easy!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
