<?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: Backups on Debian Linux</title>
	<atom:link href="http://alastairc.ac/notes/debian/backups/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Thu, 12 Jan 2012 09:29:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/notes/debian/backups/comment-page-1/#comment-33894</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Tue, 19 Feb 2008 16:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/backups/#comment-33894</guid>
		<description>Good tip on the shell variable. Looking into it, perhaps &lt;a href=&quot;http://dev.mysql.com/doc/refman/5.0/en/password-security.html&quot; rel=&quot;nofollow&quot;&gt;storing the password in an option file&lt;/a&gt; is the way to go.</description>
		<content:encoded><![CDATA[<p>Good tip on the shell variable. Looking into it, perhaps <a href="http://dev.mysql.com/doc/refman/5.0/en/password-security.html" rel="nofollow">storing the password in an option file</a> is the way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwrofij esj ferfi</title>
		<link>http://alastairc.ac/notes/debian/backups/comment-page-1/#comment-33892</link>
		<dc:creator>pwrofij esj ferfi</dc:creator>
		<pubDate>Tue, 19 Feb 2008 16:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/backups/#comment-33892</guid>
		<description>&lt;blockquote&gt;What is the alternative?&lt;/blockquote&gt;

I don&#039;t know the &#039;mysqlhotcopy&#039; tool. It should prompt for the pwd itself if not given on the command line. It&#039;s a serious bug if it does not! Note, that any user (unless restricted to incredible lengths) can see the process table. So you &lt;em&gt;really&lt;/em&gt; have to be the only one logged in.

To avoid the line popping up in your history, using bash, you may set the environment variable $HISTIGNORE to &#039; *:&amp;&#039;, and add a space before &#039;mysqlhotcopy&#039;. This setting of $HISTIGNORE does not add lines with leading space to the history. Maybe you can tweak $HISTIGNORE into never memorise lines that start with &#039;mysqlhotcopy&#039;, read bash(1).

In fact I just stubled over this page by accident and was attracted by the word Debian. I don&#039;t use any DB software, but that&#039;s another story...</description>
		<content:encoded><![CDATA[<blockquote><p>What is the alternative?</p></blockquote>
<p>I don&#8217;t know the &#8216;mysqlhotcopy&#8217; tool. It should prompt for the pwd itself if not given on the command line. It&#8217;s a serious bug if it does not! Note, that any user (unless restricted to incredible lengths) can see the process table. So you <em>really</em> have to be the only one logged in.</p>
<p>To avoid the line popping up in your history, using bash, you may set the environment variable $HISTIGNORE to &#8216; *:&amp;&#8217;, and add a space before &#8216;mysqlhotcopy&#8217;. This setting of $HISTIGNORE does not add lines with leading space to the history. Maybe you can tweak $HISTIGNORE into never memorise lines that start with &#8216;mysqlhotcopy&#8217;, read bash(1).</p>
<p>In fact I just stubled over this page by accident and was attracted by the word Debian. I don&#8217;t use any DB software, but that&#8217;s another story&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/notes/debian/backups/comment-page-1/#comment-33873</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Tue, 19 Feb 2008 14:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/backups/#comment-33873</guid>
		<description>In my case I&#039;m the only user with access to the system, however, it&#039;s a good point.

What is the alternative?</description>
		<content:encoded><![CDATA[<p>In my case I&#8217;m the only user with access to the system, however, it&#8217;s a good point.</p>
<p>What is the alternative?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwrofij esj ferfi</title>
		<link>http://alastairc.ac/notes/debian/backups/comment-page-1/#comment-33867</link>
		<dc:creator>pwrofij esj ferfi</dc:creator>
		<pubDate>Tue, 19 Feb 2008 13:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/backups/#comment-33867</guid>
		<description>Hi.

I could not find a date on this page, so I really don&#039;t know if it&#039;s still up to date/relevant.

However, I&#039;d like to point out an important security issue: Giving passwords on the command line as in

&lt;blockquote&gt;mysqlhotcopy -u root --password=RootsPassWord wordpress /mnt/backups/wordpress/;&lt;/blockquote&gt;

is almost certainly a bad idea. For two reasons:


If the process does not overwite its command line arguments immediately, they can be observed in the table of running processes (using the ps command or the /proc file system). If it does, the argument may still be visible in the timespan between process invocation and argument deletion. Furthermore altering ones command line arguments is a dirty hack.
The password is stored in plain text in your shell history. I.e., you have to take care abut (who has access to) this file even more, than about the system password file which stores only encrypted passwords. Also think about backing up your $HOME.


And I miss a preview button for the comment</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>I could not find a date on this page, so I really don&#8217;t know if it&#8217;s still up to date/relevant.</p>
<p>However, I&#8217;d like to point out an important security issue: Giving passwords on the command line as in</p>
<blockquote><p>mysqlhotcopy -u root &#8211;password=RootsPassWord wordpress /mnt/backups/wordpress/;</p></blockquote>
<p>is almost certainly a bad idea. For two reasons:</p>
<p>If the process does not overwite its command line arguments immediately, they can be observed in the table of running processes (using the ps command or the /proc file system). If it does, the argument may still be visible in the timespan between process invocation and argument deletion. Furthermore altering ones command line arguments is a dirty hack.<br />
The password is stored in plain text in your shell history. I.e., you have to take care abut (who has access to) this file even more, than about the system password file which stores only encrypted passwords. Also think about backing up your $HOME.</p>
<p>And I miss a preview button for the comment</p>
]]></content:encoded>
	</item>
</channel>
</rss>

