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

Re: private directories

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-09-16 19:56:20 CEST

David F. Newman wrote:
> On Thu, 2004-09-16 at 09:53, Ben Collins-Sussman wrote:
>> On Thu, 2004-09-16 at 08:18, David F. Newman wrote:
>>> svn co http://svn/test/trunk
>>> A trunk/test.txt
>>> Checked out revision 5.
>>> Is this a bug or a feature?
>> That's a feature. Checkouts just 'skip over' unreadable subtrees. We
>> went through a lot of work to code that.
>> If, at a future point, you suddenly gain the ability to read
>> /trunk/secret, then 'svn up' will make the directory appear in your
>> working copy.
> Subversion must be using my cached credentials since this works:
> svn co http://svn/test/trunk/secret
> A secret/test.txt
> Checked out revision 5.
> So the question becomes, why does subversion skip over /trunk/secret
> when I issue:
> svn co http://svn/test/trunk
> A trunk/test.txt
> Checked out revision 5.
> I've even tried explicitly specifying the username
> svn --username dnewman co $T/trunk
> A trunk/test.txt
> Checked out revision 5.

Subversion servers 'pull' auth from their clients. The clients have no
opportunity to 'push' auth at the server.

Hence, because your root is anonymous-readable, no auth is pulled when
checking out from the root.

One possible (admittedly hackish) workaround would be to require
authentication, and publish the existence of a "user=guest/pass=guest"


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 16 19:56:53 2004

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.