<?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: Much (more) ado about SSL</title>
	<atom:link href="http://www.standalone-sysadmin.com/blog/2009/10/much-more-ado-about-ssl/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.standalone-sysadmin.com/blog/2009/10/much-more-ado-about-ssl/</link>
	<description>A blog for IT Admins who do everything by an IT Admin who does everything</description>
	<lastBuildDate>Tue, 07 Sep 2010 20:41:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anthony</title>
		<link>http://www.standalone-sysadmin.com/blog/2009/10/much-more-ado-about-ssl/comment-page-1/#comment-3443</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Fri, 16 Oct 2009 13:44:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.standalone-sysadmin.com/blog/?p=970#comment-3443</guid>
		<description>Something else people often forget about when trying to protect their data - is it really worth protecting?  

In this case, your password to log in and make changes to the blog is of course worth protecting.  As a good sysadmin you don&#039;t use that same password on anything else (of course (heh heh,)) however you certainly don&#039;t want anyone to be able to hack into your blog and screw around with it.

At the same time the data you are pushing out to your blog is meant for public consumption anyway.  Why protect something that you&#039;re trying to make available to everyone?</description>
		<content:encoded><![CDATA[<p>Something else people often forget about when trying to protect their data &#8211; is it really worth protecting?  </p>
<p>In this case, your password to log in and make changes to the blog is of course worth protecting.  As a good sysadmin you don&#8217;t use that same password on anything else (of course (heh heh,)) however you certainly don&#8217;t want anyone to be able to hack into your blog and screw around with it.</p>
<p>At the same time the data you are pushing out to your blog is meant for public consumption anyway.  Why protect something that you&#8217;re trying to make available to everyone?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jinks</title>
		<link>http://www.standalone-sysadmin.com/blog/2009/10/much-more-ado-about-ssl/comment-page-1/#comment-3441</link>
		<dc:creator>Jinks</dc:creator>
		<pubDate>Fri, 16 Oct 2009 04:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.standalone-sysadmin.com/blog/?p=970#comment-3441</guid>
		<description>Since I didn&#039;t see it mentioned:
CACert is another great free cert provider. It&#039;s noncommercial, offers various chain of trust options through volunteers and a &lt;i&gt;very&lt;/i&gt; easy setup for basic cert needs.</description>
		<content:encoded><![CDATA[<p>Since I didn&#8217;t see it mentioned:<br />
CACert is another great free cert provider. It&#8217;s noncommercial, offers various chain of trust options through volunteers and a <i>very</i> easy setup for basic cert needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twirrim</title>
		<link>http://www.standalone-sysadmin.com/blog/2009/10/much-more-ado-about-ssl/comment-page-1/#comment-3440</link>
		<dc:creator>Twirrim</dc:creator>
		<pubDate>Fri, 16 Oct 2009 04:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.standalone-sysadmin.com/blog/?p=970#comment-3440</guid>
		<description>@dagard

Thanks for mentioning OpenVPN, a quick Google shows there is even a maemo client out there so I can secure my N810 when on public wireless, with a lot less hassle than other methods I was using.</description>
		<content:encoded><![CDATA[<p>@dagard</p>
<p>Thanks for mentioning OpenVPN, a quick Google shows there is even a maemo client out there so I can secure my N810 when on public wireless, with a lot less hassle than other methods I was using.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dagard</title>
		<link>http://www.standalone-sysadmin.com/blog/2009/10/much-more-ado-about-ssl/comment-page-1/#comment-3439</link>
		<dc:creator>dagard</dc:creator>
		<pubDate>Fri, 16 Oct 2009 03:36:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.standalone-sysadmin.com/blog/?p=970#comment-3439</guid>
		<description>OpenVPN and a good certificate have always worked pretty well for me, especially since you can masquerade it inside a normal HTTPS session.  Easy to set up, key based, so you can easily revoke logins, software available for many, many platforms (we supported 5 or 6, including 3 different flavors of Linux, at my last job), total win.</description>
		<content:encoded><![CDATA[<p>OpenVPN and a good certificate have always worked pretty well for me, especially since you can masquerade it inside a normal HTTPS session.  Easy to set up, key based, so you can easily revoke logins, software available for many, many platforms (we supported 5 or 6, including 3 different flavors of Linux, at my last job), total win.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
