<?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: Read-Only and Read-Write SVN Repositories</title>
	<atom:link href="http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/</link>
	<description>Thoughts, rants, and even some code from the mind of Barney Boisvert.</description>
	<pubDate>Thu, 20 Nov 2008 07:32:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: barneyb</title>
		<link>http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119226</link>
		<dc:creator>barneyb</dc:creator>
		<pubDate>Wed, 27 Aug 2008 20:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119226</guid>
		<description>Nic,

Nope, though you do have to ensure that Apache will not require a valid login to access the URL-space that SVN is using.  Apache does all the authentication, and it CAN do authorization as well.  If you want to use SVN to do authorization, you just need to make sure that Apache's not doing it as well.  There are use cases for having both processes do authorization, but they're not for anonymous access.</description>
		<content:encoded><![CDATA[<p>Nic,</p>
<p>Nope, though you do have to ensure that Apache will not require a valid login to access the URL-space that SVN is using.  Apache does all the authentication, and it CAN do authorization as well.  If you want to use SVN to do authorization, you just need to make sure that Apache's not doing it as well.  There are use cases for having both processes do authorization, but they're not for anonymous access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nic Cottrell</title>
		<link>http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119217</link>
		<dc:creator>Nic Cottrell</dc:creator>
		<pubDate>Wed, 27 Aug 2008 19:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119217</guid>
		<description>Ok, so there's no need to have a username "*" in the specified AuthUserFile? I assumed that apache would authenticate against that file first before passing the request onto modsvn to check the per-directory authentication.</description>
		<content:encoded><![CDATA[<p>Ok, so there's no need to have a username "*" in the specified AuthUserFile? I assumed that apache would authenticate against that file first before passing the request onto modsvn to check the per-directory authentication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: barneyb</title>
		<link>http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119190</link>
		<dc:creator>barneyb</dc:creator>
		<pubDate>Wed, 27 Aug 2008 16:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119190</guid>
		<description>Nic,

If you use an asterisk for the username, that means anonymous.  I.e. SVN won't do any authentication of it's own.  You can see that in the snippet of the AuthZ access file (line 5).  So if you try to go to the /bicycle_dashboard path in my repository, you'll just get it.  Access is read-only, but no need to authenticate with dummy credentials.  However, if you try to perform a write operation (e.g. a commit), SVN will prompt for credentials (using HTTP Basic Auth).</description>
		<content:encoded><![CDATA[<p>Nic,</p>
<p>If you use an asterisk for the username, that means anonymous.  I.e. SVN won't do any authentication of it's own.  You can see that in the snippet of the AuthZ access file (line 5).  So if you try to go to the /bicycle_dashboard path in my repository, you'll just get it.  Access is read-only, but no need to authenticate with dummy credentials.  However, if you try to perform a write operation (e.g. a commit), SVN will prompt for credentials (using HTTP Basic Auth).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nic Cottrell</title>
		<link>http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119141</link>
		<dc:creator>Nic Cottrell</dc:creator>
		<pubDate>Wed, 27 Aug 2008 12:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/2008/02/28/read-only-and-read-write-svn-repositories/#comment-119141</guid>
		<description>Would it be possible to have anonymous read-only access somehow? Or would I have to create an account in the passwords file called "anonymous" with a blank password or something to make this happen?</description>
		<content:encoded><![CDATA[<p>Would it be possible to have anonymous read-only access somehow? Or would I have to create an account in the passwords file called "anonymous" with a blank password or something to make this happen?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
