<?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 Eat Paint Studio</title>
	<atom:link href="http://eatpaintstudio.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://eatpaintstudio.com</link>
	<description>Intuitive Design for Web and Print.</description>
	<lastBuildDate>Sun, 29 Apr 2012 19:41:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>Comment on Its a big, bad World Wide Web by Emily</title>
		<link>http://eatpaintstudio.com/2012/04/its-a-big-bad-world-wide-web/#comment-448</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Sun, 29 Apr 2012 19:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://eatpaintstudio.com/?p=1348#comment-448</guid>
		<description>Thanks for your comments Jeff. I heartily disagree with your view on WordPress - it is a sophisticated CMS and absolutely not just for blogs. A good WordPress developer will be familiar with security issues that are likely to be targets (the strength of open source IS its community of developers). Removing the &quot;admin&quot; user (or taking away all priviledges) and changing the database prefix are two basic examples. 

As for passwords - using special characters for letters ($ of 5 instead of &quot;s&quot;) is just a way for users to remember their own password methodology. Dictionary words should still be avoided. 

I&#039;ll look into the podcasts you mentioned and again thanks for your input.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments Jeff. I heartily disagree with your view on WordPress &#8211; it is a sophisticated CMS and absolutely not just for blogs. A good WordPress developer will be familiar with security issues that are likely to be targets (the strength of open source IS its community of developers). Removing the &#8220;admin&#8221; user (or taking away all priviledges) and changing the database prefix are two basic examples. </p>
<p>As for passwords &#8211; using special characters for letters ($ of 5 instead of &#8220;s&#8221;) is just a way for users to remember their own password methodology. Dictionary words should still be avoided. </p>
<p>I&#8217;ll look into the podcasts you mentioned and again thanks for your input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Its a big, bad World Wide Web by Jeff</title>
		<link>http://eatpaintstudio.com/2012/04/its-a-big-bad-world-wide-web/#comment-446</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Sun, 29 Apr 2012 19:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://eatpaintstudio.com/?p=1348#comment-446</guid>
		<description>Good summary! Too bad so many websites and devices don&#039;t allow characters outside the alphanumeric sets. That would make things so much more secure. And too bad WordPress has become a low-tech alternative to real websites for so many businesses, when it&#039;s also so unsecure. It was designed as a blogging platform and every hacker on the planet knows its flaws.

Although I would say your suggestions about replacing s with $, etc. are incorrect. Hackers have had all those alternatives in their cracking algorithms for 10 years. They provide no protection whatsoever.

You should check out the Security Now podcasts about secure passwords, episodes 303 &amp; 304 from June 2011 (with Leo Laporte and Steve Gibson).

Best regards!</description>
		<content:encoded><![CDATA[<p>Good summary! Too bad so many websites and devices don&#8217;t allow characters outside the alphanumeric sets. That would make things so much more secure. And too bad WordPress has become a low-tech alternative to real websites for so many businesses, when it&#8217;s also so unsecure. It was designed as a blogging platform and every hacker on the planet knows its flaws.</p>
<p>Although I would say your suggestions about replacing s with $, etc. are incorrect. Hackers have had all those alternatives in their cracking algorithms for 10 years. They provide no protection whatsoever.</p>
<p>You should check out the Security Now podcasts about secure passwords, episodes 303 &amp; 304 from June 2011 (with Leo Laporte and Steve Gibson).</p>
<p>Best regards!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2010 Ravenswood ArtWalk Poster Design by eps_chicago</title>
		<link>http://eatpaintstudio.com/2010/08/ravenswood-artwalk-poster/#comment-3</link>
		<dc:creator>eps_chicago</dc:creator>
		<pubDate>Sat, 21 Aug 2010 00:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://eatpaintstudio.wordpress.com/?p=329#comment-3</guid>
		<description>Thanks Nancy! I like it too.</description>
		<content:encoded><![CDATA[<p>Thanks Nancy! I like it too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2010 Ravenswood ArtWalk Poster Design by Nancy Charak</title>
		<link>http://eatpaintstudio.com/2010/08/ravenswood-artwalk-poster/#comment-2</link>
		<dc:creator>Nancy Charak</dc:creator>
		<pubDate>Fri, 20 Aug 2010 23:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://eatpaintstudio.wordpress.com/?p=329#comment-2</guid>
		<description>Well done. I like it a lot. Bye-bye raven nevermore,</description>
		<content:encoded><![CDATA[<p>Well done. I like it a lot. Bye-bye raven nevermore,</p>
]]></content:encoded>
	</item>
</channel>
</rss>

