<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: MySQL Client Security on the Command Line</title>
	<link>http://damonparker.org/blog/2006/06/23/mysql-client-security-on-the-command-line/</link>
	<description>mental spew</description>
	<pubDate>Wed, 07 Jan 2009 21:29:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: barnaby jones</title>
		<link>http://damonparker.org/blog/2006/06/23/mysql-client-security-on-the-command-line/#comment-25954</link>
		<author>barnaby jones</author>
		<pubDate>Tue, 25 Mar 2008 00:27:23 +0000</pubDate>
		<guid>http://damonparker.org/blog/2006/06/23/mysql-client-security-on-the-command-line/#comment-25954</guid>
					<description>good point.

likewise, mysql client logs all commands to $HOME/.mysql_history by default (at least on debian), which exposes all passwords that you set on the mysql shell to all who can read this file.

cheerio!</description>
		<content:encoded><![CDATA[<p>good point.</p>
<p>likewise, mysql client logs all commands to $HOME/.mysql_history by default (at least on debian), which exposes all passwords that you set on the mysql shell to all who can read this file.</p>
<p>cheerio!</p>
]]></content:encoded>
				</item>
</channel>
</rss>
