<?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: Setup SVN with SSL using Apache2 on Linux (Debian)</title>
	<atom:link href="http://slunked.com/blog/2010/03/setup-svn-ssl-apache2-debian/feed/" rel="self" type="application/rss+xml" />
	<link>http://slunked.com/blog/2010/03/setup-svn-ssl-apache2-debian/</link>
	<description>Providing clear instructions and tutorials to coding users!</description>
	<lastBuildDate>Fri, 13 Apr 2012 04:58:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Frost</title>
		<link>http://slunked.com/blog/2010/03/setup-svn-ssl-apache2-debian/comment-page-1/#comment-3</link>
		<dc:creator>Frost</dc:creator>
		<pubDate>Sat, 20 Mar 2010 01:56:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.slunked.com/blog/?p=159#comment-3</guid>
		<description>Thanks for the comment. However, I do not know what you are talking about. I do use the .authz file and show how to create it on the second page you should see it under the vhosts declaration under the Location /svn for the DAV setup.  I also go over how to generate the .authz file. As far as the name for it, I am not sure how that is not the most descriptive, but feel free to name it whatever you want. As long as it is under the vhosts declaration (if you want to make people authenticate) there should not be a problem. This is just how I set it up :)

If this is still un-clear let me know, as I think you may have glazed over that section. Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment. However, I do not know what you are talking about. I do use the .authz file and show how to create it on the second page you should see it under the vhosts declaration under the Location /svn for the DAV setup.  I also go over how to generate the .authz file. As far as the name for it, I am not sure how that is not the most descriptive, but feel free to name it whatever you want. As long as it is under the vhosts declaration (if you want to make people authenticate) there should not be a problem. This is just how I set it up <img src='http://slunked.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>If this is still un-clear let me know, as I think you may have glazed over that section. Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trq</title>
		<link>http://slunked.com/blog/2010/03/setup-svn-ssl-apache2-debian/comment-page-1/#comment-2</link>
		<dc:creator>trq</dc:creator>
		<pubDate>Sat, 20 Mar 2010 01:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.slunked.com/blog/?p=159#comment-2</guid>
		<description>Just thought I should mention that naming your htpasswd file *.authz probably isn&#039;t the most descriptive seeing as though your not using authz in this setup.

You should look into authz and maybe write a followup blog describing how you can use it to grant different access rights to different users on a per path basis.</description>
		<content:encoded><![CDATA[<p>Just thought I should mention that naming your htpasswd file *.authz probably isn&#8217;t the most descriptive seeing as though your not using authz in this setup.</p>
<p>You should look into authz and maybe write a followup blog describing how you can use it to grant different access rights to different users on a per path basis.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

