<?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"
	>
<channel>
	<title>Comments on: Secure mysql replication between colos over an ssh tunnel</title>
	<atom:link href="http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/</link>
	<description>A blog about killer code</description>
	<pubDate>Tue, 06 Jan 2009 04:46:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: PHP Programming India</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-243</link>
		<dc:creator>PHP Programming India</dc:creator>
		<pubDate>Wed, 15 Oct 2008 11:49:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-243</guid>
		<description>Very informative.  Thanks for the information!

Raj Malhotra
PHP Programming India</description>
		<content:encoded><![CDATA[<p>Very informative.  Thanks for the information!</p>
<p>Raj Malhotra<br />
PHP Programming India</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaisen</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-242</link>
		<dc:creator>jaisen</dc:creator>
		<pubDate>Mon, 13 Oct 2008 20:53:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-242</guid>
		<description>@Tom, Thanks for pointing that out - I'll add that option to the post.  While this addresses #1 and #3, there's still security to be gained by not having mysql listening publicly.

I'm assuming that there's some ssh entry point to the machine (if not directly through a firewall).  So having ssh open on some port is a given.  The more applications you have listening publicly the more chances you have for being exploited.  Note, I'm not saying Apache is (or isn't) more secure than MySql, but the more entry points the more likely something can happen.

Personally, I prefer ports 80, 443 and a non standard port for ssh.</description>
		<content:encoded><![CDATA[<p>@Tom, Thanks for pointing that out - I&#8217;ll add that option to the post.  While this addresses #1 and #3, there&#8217;s still security to be gained by not having mysql listening publicly.</p>
<p>I&#8217;m assuming that there&#8217;s some ssh entry point to the machine (if not directly through a firewall).  So having ssh open on some port is a given.  The more applications you have listening publicly the more chances you have for being exploited.  Note, I&#8217;m not saying Apache is (or isn&#8217;t) more secure than MySql, but the more entry points the more likely something can happen.</p>
<p>Personally, I prefer ports 80, 443 and a non standard port for ssh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-241</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 13 Oct 2008 20:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-241</guid>
		<description>Built in MySQL encryption:  http://dev.mysql.com/doc/refman/5.0/en/secure-using-ssl.html


Having port 3306 open is probably just as secure or insecure as having a random ssh port open somewhere.</description>
		<content:encoded><![CDATA[<p>Built in MySQL encryption:  <a href="http://dev.mysql.com/doc/refman/5.0/en/secure-using-ssl.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/secure-using-ssl.html</a></p>
<p>Having port 3306 open is probably just as secure or insecure as having a random ssh port open somewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaisen</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-240</link>
		<dc:creator>jaisen</dc:creator>
		<pubDate>Sat, 11 Oct 2008 05:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-240</guid>
		<description>@Brandon, Thanks for the tips.  I'll definitely check out the two posts you mentioned (and subscribe via RSS).</description>
		<content:encoded><![CDATA[<p>@Brandon, Thanks for the tips.  I&#8217;ll definitely check out the two posts you mentioned (and subscribe via RSS).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaisen</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-239</link>
		<dc:creator>jaisen</dc:creator>
		<pubDate>Sat, 11 Oct 2008 05:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-239</guid>
		<description>@Tom, not sure what built in encryption support you're referring to.  Even if MySql did have some sort of encryption support this method still allows you to keep MySql from listening publicly on port 3306.</description>
		<content:encoded><![CDATA[<p>@Tom, not sure what built in encryption support you&#8217;re referring to.  Even if MySql did have some sort of encryption support this method still allows you to keep MySql from listening publicly on port 3306.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-238</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 11 Oct 2008 01:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-238</guid>
		<description>Or, you could just use MySQL's built in encryption support...

What is the point of this?</description>
		<content:encoded><![CDATA[<p>Or, you could just use MySQL&#8217;s built in encryption support&#8230;</p>
<p>What is the point of this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Checketts</title>
		<link>http://www.jaisenmathai.com/blog/2008/10/10/secure-mysql-replication-between-colos-over-an-ssh-tunnel/#comment-237</link>
		<dc:creator>Brandon Checketts</dc:creator>
		<pubDate>Sat, 11 Oct 2008 00:32:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=37#comment-237</guid>
		<description>Hi.  Glad that you find my instructions helpful.  I have been running a server like this with tunnels to 3 other servers for several months now and it works very well.  

The only thing I have noticed, is that if the connection between the server goes down for a while, then there can get to be multiple 'check_tunnel' scripts running that have to be killed manually.   Other than that, I've had the connection between the servers die multiple times, and replication always starts right back up.

You might also be interested in the script I created to &lt;a href="http://www.brandonchecketts.com/archives/checking-mysql-replication" rel="nofollow"&gt;Monitor the replication&lt;/a&gt; to ensure that it doesn't get behind.

Also, you'll want to &lt;a href="http://www.brandonchecketts.com/archives/compression-for-mysql-replication" rel="nofollow"&gt;Enable replication compression&lt;/a&gt; between those servers to minimize the bandwidth used.</description>
		<content:encoded><![CDATA[<p>Hi.  Glad that you find my instructions helpful.  I have been running a server like this with tunnels to 3 other servers for several months now and it works very well.  </p>
<p>The only thing I have noticed, is that if the connection between the server goes down for a while, then there can get to be multiple &#8216;check_tunnel&#8217; scripts running that have to be killed manually.   Other than that, I&#8217;ve had the connection between the servers die multiple times, and replication always starts right back up.</p>
<p>You might also be interested in the script I created to <a href="http://www.brandonchecketts.com/archives/checking-mysql-replication" rel="nofollow">Monitor the replication</a> to ensure that it doesn&#8217;t get behind.</p>
<p>Also, you&#8217;ll want to <a href="http://www.brandonchecketts.com/archives/compression-for-mysql-replication" rel="nofollow">Enable replication compression</a> between those servers to minimize the bandwidth used.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
