[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: AW: Web site: checkout or export?

From: Thomas Harold <thomas-lists_at_nybeta.com>
Date: Fri, 29 Jul 2011 07:54:45 -0400

On 7/27/2011 8:57 AM, Markus Schaber wrote:
> Hi, Andy,
> Von: Andy Canfield [mailto:andy.canfield_at_pimco.mobi]
>> - Using 'svn checkout', the working web site will have the
>> subversion control files in the .svn subdirectory, which might be a
>> security hole.
> You could use some pattern based access control (Apache is very
> configurable in that respect) to prevent remote access to all pathes
> containing .svn in their url.
> And the security hole should be not that large, as the .svn directory
> usually does not contain any authentication information.
> Subversion 1.7 will further improve on that situation, you only have
> a single .svn directory then. And you can use the trick of directing
> the webserver to a subdir of your working copy, so the .svn directory
> is completely out of the web servers path.

Alternately, if it is a Linux based host, you can use a tool like FSVS
which also doesn't create the .svn metadata directories in the file
system. (Although we use FSVS more in a tripwire / change log fashion
on our servers to track and note configuration changes.) But SVN 1.7
with a central .svn folder will also make things much easier.

One thing that I do wish SVN would add to their export command would be
a "sync" where it would only bring down files that are actually changed
content instead of bringing everything down. Which would make the SVN
export method more bandwidth friendly.
Received on 2011-07-29 13:55:32 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.