<?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 for Nim&#039;s braindump</title>
	<atom:link href="http://blog.lick-me.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.lick-me.org</link>
	<description>Swords, code and a dirty mind!</description>
	<lastBuildDate>Fri, 15 Mar 2013 00:11:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Howto: soapUI integration tests with Maven by jr</title>
		<link>http://blog.lick-me.org/2010/02/howto-soapui-integration-tests-with-maven/comment-page-1/#comment-688</link>
		<dc:creator>jr</dc:creator>
		<pubDate>Fri, 15 Mar 2013 00:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=118#comment-688</guid>
		<description><![CDATA[Thanks for the post!  Very helpful.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the post!  Very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gnuplot data analysis, real world example by blarp</title>
		<link>http://blog.lick-me.org/2012/12/gnuplot-data-analysis-real-world-example/comment-page-1/#comment-687</link>
		<dc:creator>blarp</dc:creator>
		<pubDate>Thu, 14 Mar 2013 17:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=298#comment-687</guid>
		<description><![CDATA[interested to see those changes]]></description>
		<content:encoded><![CDATA[<p>interested to see those changes</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repeat after me: MySQL is not a filesystem by Nim</title>
		<link>http://blog.lick-me.org/2013/01/repeat-after-me-mysql-is-not-a-filesystem/comment-page-1/#comment-599</link>
		<dc:creator>Nim</dc:creator>
		<pubDate>Mon, 14 Jan 2013 22:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=333#comment-599</guid>
		<description><![CDATA[True. Still doesn&#039;t make MySQL any more of a filesystem though. When I have the time I might have a look at the effect of large blobs on overal database performance under load. Might make for interesting results.]]></description>
		<content:encoded><![CDATA[<p>True. Still doesn&#8217;t make MySQL any more of a filesystem though. When I have the time I might have a look at the effect of large blobs on overal database performance under load. Might make for interesting results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repeat after me: MySQL is not a filesystem by Martyr2</title>
		<link>http://blog.lick-me.org/2013/01/repeat-after-me-mysql-is-not-a-filesystem/comment-page-1/#comment-598</link>
		<dc:creator>Martyr2</dc:creator>
		<pubDate>Mon, 14 Jan 2013 18:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=333#comment-598</guid>
		<description><![CDATA[Good article. I wrote about this topic back in 2011 in response to an increased &quot;chatter&quot; of storing images into MySQL. 

http://www.coderslexicon.com/inserting-images-into-mysql-and-retrieving-them-using-php/

My research came to the same conclusions that large images should be left out of BLOB fields. I did notice that if the imagery was small, say around an icon size that most databases handle this amount fairly well. 

However, my stance parallels yours. Leave image data out of it. You gain advantages to having path data to images as well like being able to search the file name etc.

Thanks! :)]]></description>
		<content:encoded><![CDATA[<p>Good article. I wrote about this topic back in 2011 in response to an increased &#8220;chatter&#8221; of storing images into MySQL. </p>
<p><a href="http://www.coderslexicon.com/inserting-images-into-mysql-and-retrieving-them-using-php/" rel="nofollow">http://www.coderslexicon.com/inserting-images-into-mysql-and-retrieving-them-using-php/</a></p>
<p>My research came to the same conclusions that large images should be left out of BLOB fields. I did notice that if the imagery was small, say around an icon size that most databases handle this amount fairly well. </p>
<p>However, my stance parallels yours. Leave image data out of it. You gain advantages to having path data to images as well like being able to search the file name etc.</p>
<p>Thanks! <img src='http://blog.lick-me.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repeat after me: MySQL is not a filesystem by Justin Dalton</title>
		<link>http://blog.lick-me.org/2013/01/repeat-after-me-mysql-is-not-a-filesystem/comment-page-1/#comment-597</link>
		<dc:creator>Justin Dalton</dc:creator>
		<pubDate>Mon, 14 Jan 2013 15:40:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=333#comment-597</guid>
		<description><![CDATA[I agree, having tried this a long time ago.  Any time you have a situation where you would need to &quot;index&quot; an image in a database you are better off to store the image in the file system and use the database to store its location (file name) in a database table and using the location to perform whatever operations you need to perform on the image.]]></description>
		<content:encoded><![CDATA[<p>I agree, having tried this a long time ago.  Any time you have a situation where you would need to &#8220;index&#8221; an image in a database you are better off to store the image in the file system and use the database to store its location (file name) in a database table and using the location to perform whatever operations you need to perform on the image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repeat after me: MySQL is not a filesystem by Max Toro</title>
		<link>http://blog.lick-me.org/2013/01/repeat-after-me-mysql-is-not-a-filesystem/comment-page-1/#comment-596</link>
		<dc:creator>Max Toro</dc:creator>
		<pubDate>Sun, 13 Jan 2013 22:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=333#comment-596</guid>
		<description><![CDATA[It&#039;s not about where you store images, it&#039;s about your strategy to serve them. You could have images in the database and use output cache on the web server.

Of course it slows backups, because your are backing up everything, which also simplifies backups, only one backup to do, you don&#039;t have to worry about files.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s not about where you store images, it&#8217;s about your strategy to serve them. You could have images in the database and use output cache on the web server.</p>
<p>Of course it slows backups, because your are backing up everything, which also simplifies backups, only one backup to do, you don&#8217;t have to worry about files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gnuplot data analysis, real world example by Nim</title>
		<link>http://blog.lick-me.org/2012/12/gnuplot-data-analysis-real-world-example/comment-page-1/#comment-589</link>
		<dc:creator>Nim</dc:creator>
		<pubDate>Sat, 05 Jan 2013 17:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=298#comment-589</guid>
		<description><![CDATA[I&#039;ve made a couple of updates to whole process, eliminating the need for calling shell scripts from withun gnuplot (though it remains an interesting illustration of the possibility). Will update this post to reflect those changes soonish.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve made a couple of updates to whole process, eliminating the need for calling shell scripts from withun gnuplot (though it remains an interesting illustration of the possibility). Will update this post to reflect those changes soonish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SSH Gateway Shenanigans by Nim</title>
		<link>http://blog.lick-me.org/2012/06/ssh-gateway-shenanigans/comment-page-1/#comment-283</link>
		<dc:creator>Nim</dc:creator>
		<pubDate>Sun, 01 Jul 2012 13:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=264#comment-283</guid>
		<description><![CDATA[@RyanC: I&#039;ve updated the original post to address your concerns. Thanks again for pointing those out!]]></description>
		<content:encoded><![CDATA[<p>@RyanC: I&#8217;ve updated the original post to address your concerns. Thanks again for pointing those out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SSH Gateway Shenanigans by Nim</title>
		<link>http://blog.lick-me.org/2012/06/ssh-gateway-shenanigans/comment-page-1/#comment-257</link>
		<dc:creator>Nim</dc:creator>
		<pubDate>Tue, 26 Jun 2012 22:17:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=264#comment-257</guid>
		<description><![CDATA[@RyanC: I didn&#039;t really intend to prevent any escaping/command execution, but I admit that I completely overlooked that little SSH gem. I&#039;ll try to spend some time testing this over the weekend. Thanks for the tip! Much appreciated!]]></description>
		<content:encoded><![CDATA[<p>@RyanC: I didn&#8217;t really intend to prevent any escaping/command execution, but I admit that I completely overlooked that little SSH gem. I&#8217;ll try to spend some time testing this over the weekend. Thanks for the tip! Much appreciated!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SSH Gateway Shenanigans by RyanC</title>
		<link>http://blog.lick-me.org/2012/06/ssh-gateway-shenanigans/comment-page-1/#comment-249</link>
		<dc:creator>RyanC</dc:creator>
		<pubDate>Mon, 25 Jun 2012 22:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lick-me.org/?p=264#comment-249</guid>
		<description><![CDATA[I&#039;m not sure if you intended to prevent it, but the script you list here allows a user to run arbitrary commands as the foo user on physical.box via two methods.

1) ssh foo@physical.box, then type &#039;~~C&#039;, then &#039;!command executed on physical.box&#039;.

Running ssh to the vm with -e none on the command line and PermitLocalCommand no in the config file will stop this.


2) ssh foo@physical.box &#039;`command executed on physical.box`&#039;

I don&#039;t know of a robust way to avoid this one in bash, but the following should be safe:

#!/usr/bin/perl
my $user = shift(@ARGV);
my $host = shift(@ARGV);

my $command = $ENV{SSH_ORIGINAL_COMMAND};
exec(&#039;/usr/bin/passwd&#039;) if ($command eq &#039;passwd&#039;);
exec(&#039;/usr/bin/ssh&#039;, &#039;-l&#039;, $user, $host, $SSH_ORIGINAL_COMMAND);]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure if you intended to prevent it, but the script you list here allows a user to run arbitrary commands as the foo user on physical.box via two methods.</p>
<p>1) ssh <a href="mailto:foo@physical.box">foo@physical.box</a>, then type &#8216;~~C&#8217;, then &#8216;!command executed on physical.box&#8217;.</p>
<p>Running ssh to the vm with -e none on the command line and PermitLocalCommand no in the config file will stop this.</p>
<p>2) ssh <a href="mailto:foo@physical.box">foo@physical.box</a> &#8216;`command executed on physical.box`&#8217;</p>
<p>I don&#8217;t know of a robust way to avoid this one in bash, but the following should be safe:</p>
<p>#!/usr/bin/perl<br />
my $user = shift(@ARGV);<br />
my $host = shift(@ARGV);</p>
<p>my $command = $ENV{SSH_ORIGINAL_COMMAND};<br />
exec(&#8216;/usr/bin/passwd&#8217;) if ($command eq &#8216;passwd&#8217;);<br />
exec(&#8216;/usr/bin/ssh&#8217;, &#8216;-l&#8217;, $user, $host, $SSH_ORIGINAL_COMMAND);</p>
]]></content:encoded>
	</item>
</channel>
</rss>
