<?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 Blog</title>
	<atom:link href="http://blog.builtbyprime.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.builtbyprime.com</link>
	<description>Prime Studios</description>
	<lastBuildDate>Sat, 18 Dec 2010 19:00:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>Comment on Fire and Ice: Studio Fun and Photo Retouching by Prime Studios</title>
		<link>http://mattgaidica.com/fire-and-ice-photo-retouching/comment-page-1#comment-66</link>
		<dc:creator>Prime Studios</dc:creator>
		<pubDate>Sat, 18 Dec 2010 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=1347#comment-66</guid>
		<description>I will relay that comment to Bobby J., i&#039;m sure he will be flattered lol!</description>
		<content:encoded><![CDATA[<p>I will relay that comment to Bobby J., i&#8217;m sure he will be flattered lol!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fire and Ice: Studio Fun and Photo Retouching by Lois Carrie Bez</title>
		<link>http://mattgaidica.com/fire-and-ice-photo-retouching/comment-page-1#comment-65</link>
		<dc:creator>Lois Carrie Bez</dc:creator>
		<pubDate>Sat, 18 Dec 2010 13:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=1347#comment-65</guid>
		<description>So cool to see body sculpting done, even to men.  Sir, your forearms are too muscular.  Zip, zip.  Thanks for sharing the process.  Great photo.</description>
		<content:encoded><![CDATA[<p>So cool to see body sculpting done, even to men.  Sir, your forearms are too muscular.  Zip, zip.  Thanks for sharing the process.  Great photo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSRF Protection in Code Igniter using Form Tokens by Prime Studios</title>
		<link>http://blog.builtbyprime.com/security/csrf-protection-in-code-igniter-using-form-tokens/comment-page-1#comment-63</link>
		<dc:creator>Prime Studios</dc:creator>
		<pubDate>Sun, 07 Nov 2010 23:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=550#comment-63</guid>
		<description>Most definitely. If you were an admin, and your cookie is sitting in your browser to validate you, you could be tricked into submitting a form on another website, which triggers a &quot;change price&quot; action on your admin site, which would be bad. Thats just one example, and while admin forms are a little tighter because only a select few might have access to the form&#039;s code, and know its vulnerabilities, I wouldn&#039;t bank on that stopping anyone!</description>
		<content:encoded><![CDATA[<p>Most definitely. If you were an admin, and your cookie is sitting in your browser to validate you, you could be tricked into submitting a form on another website, which triggers a &#8220;change price&#8221; action on your admin site, which would be bad. Thats just one example, and while admin forms are a little tighter because only a select few might have access to the form&#39;s code, and know its vulnerabilities, I wouldn&#39;t bank on that stopping anyone!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSRF Protection in Code Igniter using Form Tokens by Matt</title>
		<link>http://blog.builtbyprime.com/security/csrf-protection-in-code-igniter-using-form-tokens/comment-page-1#comment-62</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 07 Nov 2010 01:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=550#comment-62</guid>
		<description>One more question - what about administration panel forms? (e.g. add new product, add new category etc.)</description>
		<content:encoded><![CDATA[<p>One more question &#8211; what about administration panel forms? (e.g. add new product, add new category etc.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSRF Protection in Code Igniter using Form Tokens by Matt</title>
		<link>http://blog.builtbyprime.com/security/csrf-protection-in-code-igniter-using-form-tokens/comment-page-1#comment-61</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 03 Nov 2010 20:29:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=550#comment-61</guid>
		<description>ok,that sounds reasonable.&lt;br&gt;Thanks a lot, your tutorial was really helpful.&lt;br&gt;</description>
		<content:encoded><![CDATA[<p>ok,that sounds reasonable.<br />Thanks a lot, your tutorial was really helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSRF Protection in Code Igniter using Form Tokens by Prime Studios</title>
		<link>http://blog.builtbyprime.com/security/csrf-protection-in-code-igniter-using-form-tokens/comment-page-1#comment-60</link>
		<dc:creator>Prime Studios</dc:creator>
		<pubDate>Wed, 03 Nov 2010 19:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=550#comment-60</guid>
		<description>Thats a good question, and debatable. I typically put a token on each form, just because once it is built into the framework it is easy to do and it keeps all your code similar. It is especially important on e-commerce websites because you don&#039;t want a website other than yours to be able to POST form information to your scripts. For instance, if you have a cookie in your browser to keep you logged into your favorite online store, clicking a malicious form on another website could POST to your online store site and execute a function like &quot;add to cart&quot; or &quot;checkout&quot;, provided it posts valid information, all because your browser is technically logged in that website. With a token (or nonce), it makes this very difficult.&lt;br&gt;&lt;br&gt;Where I don&#039;t use tokens is things like &quot;logout&quot; links, or maybe &quot;remove from cart&quot; anchors.. because its not the end of the world if those are somehow compromised.</description>
		<content:encoded><![CDATA[<p>Thats a good question, and debatable. I typically put a token on each form, just because once it is built into the framework it is easy to do and it keeps all your code similar. It is especially important on e-commerce websites because you don&#39;t want a website other than yours to be able to POST form information to your scripts. For instance, if you have a cookie in your browser to keep you logged into your favorite online store, clicking a malicious form on another website could POST to your online store site and execute a function like &#8220;add to cart&#8221; or &#8220;checkout&#8221;, provided it posts valid information, all because your browser is technically logged in that website. With a token (or nonce), it makes this very difficult.</p>
<p>Where I don&#39;t use tokens is things like &#8220;logout&#8221; links, or maybe &#8220;remove from cart&#8221; anchors.. because its not the end of the world if those are somehow compromised.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSRF Protection in Code Igniter using Form Tokens by Matt</title>
		<link>http://blog.builtbyprime.com/security/csrf-protection-in-code-igniter-using-form-tokens/comment-page-1#comment-59</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 03 Nov 2010 11:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=550#comment-59</guid>
		<description>Hi,&lt;br&gt;Should all forms on a website be protected with a token? (For example on a ecommerce website there are many types of forms: add to cart, request a printed catalogue, enquiry form, checkout/order etc.; which of these need a token?)</description>
		<content:encoded><![CDATA[<p>Hi,<br />Should all forms on a website be protected with a token? (For example on a ecommerce website there are many types of forms: add to cart, request a printed catalogue, enquiry form, checkout/order etc.; which of these need a token?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 10 Handy Camera Bag Items by Janet Creque</title>
		<link>http://mattgaidica.com/10-handy-camera-bag-items/comment-page-1#comment-58</link>
		<dc:creator>Janet Creque</dc:creator>
		<pubDate>Mon, 01 Nov 2010 04:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=96#comment-58</guid>
		<description>Great post!!  Definitely going to add a couple things to my camera bag!</description>
		<content:encoded><![CDATA[<p>Great post!!  Definitely going to add a couple things to my camera bag!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding Google Quick-add to Anything: The Textdate PHP Class by Prime Studios</title>
		<link>http://blog.builtbyprime.com/php/adding-google-quick-add-to-anything-the-textdate-php-class/comment-page-1#comment-55</link>
		<dc:creator>Prime Studios</dc:creator>
		<pubDate>Sat, 09 Oct 2010 08:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=979#comment-55</guid>
		<description>Good question, we used a variable for the tee time interval (which is usually 8 minutes for a golf course), and so it defaulted to scheduling events for exactly that amount of time. Then when a user requests to play at that time, if it is taken, we give a warning and suggest the closest open tee time. So with Google, you will just query your Calendar and for anything within that time range, and go from there. On top of that, you can add custom data to the event for amount of players, because some golf courses will put two pairs of people on the same tee time. I didn&#039;t post the link to the course, but I can email it if you just contact us from our homepage footer (I didn&#039;t want people making fake tee times!). Thanks and good luck.</description>
		<content:encoded><![CDATA[<p>Good question, we used a variable for the tee time interval (which is usually 8 minutes for a golf course), and so it defaulted to scheduling events for exactly that amount of time. Then when a user requests to play at that time, if it is taken, we give a warning and suggest the closest open tee time. So with Google, you will just query your Calendar and for anything within that time range, and go from there. On top of that, you can add custom data to the event for amount of players, because some golf courses will put two pairs of people on the same tee time. I didn&#39;t post the link to the course, but I can email it if you just contact us from our homepage footer (I didn&#39;t want people making fake tee times!). Thanks and good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding Google Quick-add to Anything: The Textdate PHP Class by Altbiers</title>
		<link>http://blog.builtbyprime.com/php/adding-google-quick-add-to-anything-the-textdate-php-class/comment-page-1#comment-56</link>
		<dc:creator>Altbiers</dc:creator>
		<pubDate>Sat, 09 Oct 2010 08:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.primestudiosllc.com/?p=979#comment-56</guid>
		<description>A friend of mine recently bought a golf course and I am trying to figure out how to do tee times with google&#039;s calendar as well.  What did you do if there were people trying to book at the same time?  Did you set up 10 minute intervals?</description>
		<content:encoded><![CDATA[<p>A friend of mine recently bought a golf course and I am trying to figure out how to do tee times with google&#39;s calendar as well.  What did you do if there were people trying to book at the same time?  Did you set up 10 minute intervals?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

