<?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: Password Protecting a Podcast</title>
	<atom:link href="http://www.lemonzdream.com/blog/2006/02/20/password-protecting-a-podcast/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lemonzdream.com/blog/2006/02/20/password-protecting-a-podcast/</link>
	<description>...</description>
	<pubDate>Tue, 06 Jan 2009 09:51:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Mighty Seek - Web Application Security Podcast and Blog &#187; Blog Archive &#187; For-Pay Only Podcasting (Password Protected)</title>
		<link>http://www.lemonzdream.com/blog/2006/02/20/password-protecting-a-podcast/#comment-2747</link>
		<dc:creator>Mighty Seek - Web Application Security Podcast and Blog &#187; Blog Archive &#187; For-Pay Only Podcasting (Password Protected)</dc:creator>
		<pubDate>Thu, 14 Sep 2006 18:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.potionfactory.com/blog/2006/02/20/password-protecting-a-podcast/#comment-2747</guid>
		<description>&lt;p&gt;[...] * Just found out about another blogger who did a write up here [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] * Just found out about another blogger who did a write up here [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff &#187; RSS Feeds of WebCT Content</title>
		<link>http://www.lemonzdream.com/blog/2006/02/20/password-protecting-a-podcast/#comment-224</link>
		<dc:creator>Jeff &#187; RSS Feeds of WebCT Content</dc:creator>
		<pubDate>Thu, 20 Apr 2006 04:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.potionfactory.com/blog/2006/02/20/password-protecting-a-podcast/#comment-224</guid>
		<description>&lt;p&gt;[...] Ideally in step 4 it would be nice to wrap some authentication around this whole thing.Â  Authentication seems to be supported in a handful of RSS readers and podcast clients, mainly for standard HTTP authentication.Â  Potion Factory walks through the steps of setting up a password protected podcast.Â  Bottom line is that some form of restriction should be available should the instructor wish to restrict access to students only. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Ideally in step 4 it would be nice to wrap some authentication around this whole thing.Â  Authentication seems to be supported in a handful of RSS readers and podcast clients, mainly for standard HTTP authentication.Â  Potion Factory walks through the steps of setting up a password protected podcast.Â  Bottom line is that some form of restriction should be available should the instructor wish to restrict access to students only. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reinvented Blog &#187; Blog Archive &#187; Tips for Password Protecting Your Feed</title>
		<link>http://www.lemonzdream.com/blog/2006/02/20/password-protecting-a-podcast/#comment-119</link>
		<dc:creator>Reinvented Blog &#187; Blog Archive &#187; Tips for Password Protecting Your Feed</dc:creator>
		<pubDate>Wed, 22 Mar 2006 19:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.potionfactory.com/blog/2006/02/20/password-protecting-a-podcast/#comment-119</guid>
		<description>&lt;p&gt;[...] I get asked how to password protect feeds in general every few months and Potion Factory&#8217;s Andy Kim has written how to password protect a podcast for use in iTunes. The same method can be used to password protect any feed. In a nutshell, you can have your web server require HTTP authentication for the directory where the feed and any enclosure files reside. Here are some instructions on how to set up this authentication: Comprehensive guide to .htaccess [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I get asked how to password protect feeds in general every few months and Potion Factory&#8217;s Andy Kim has written how to password protect a podcast for use in iTunes. The same method can be used to password protect any feed. In a nutshell, you can have your web server require HTTP authentication for the directory where the feed and any enclosure files reside. Here are some instructions on how to set up this authentication: Comprehensive guide to .htaccess [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
