You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by nick vajberg <ni...@yahoo.dk> on 2004/03/11 09:07:50 UTC
VS.NET and ".svn" is a *non-issue*
I see a lot of confusion regarding VS.NET 200x and the
".svn" directories. While I hate the .svn directories
in general, VS.NET have absolutely no problem with
them. Read along.
The "problem" is IIS6 which M$ patched to disallow
paths containing dots and they did so for security
reasons (...oh my, what a hack). So waiting for
Whidbey won't do any good.
Now, this is only the DEFAULT behaviour and can be
easily worked around (as with other M$ security
patches ;-)
The first thing to try is enabling parent path
navigation:
http://support.microsoft.com/?id=332117
If that doesn't work, then get UrlScan 2.5 from
Microsoft and configure it with AllowDotInPath=1 in
the ini-file.
UrlScan is here:
(http://www.microsoft.com/downloads/details.aspx?FamilyId=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en)
NEVER EVER use any of the two suggestions above in
Internet-production environments.
That said, I hope Subversion will someday have
something better than the .svn directories. They are
eating my hard drive and driving my tools nuts.
My suggestions is: Do NOT add support for "_svn". Some
tools will probably have problem with those too.
Rather, focus on replacing the entire .svn scheme with
something less insane.
Thanks.
Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: VS.NET and ".svn" is a *non-issue*
Posted by "Brian W. Fitzpatrick" <fi...@red-bean.com>.
On Fri, 2004-03-12 at 11:28, Justin Erenkrantz wrote:
> --On Friday, March 12, 2004 12:22 PM -0500 Greg Hudson <gh...@MIT.EDU> wrote:
>
> > On Fri, 2004-03-12 at 12:20, Brian W. Fitzpatrick wrote:
> >> Nick, thank you a million. I'm putting this into the FAQ right now!
> >
> > Um, minor problem: I don't think it's true.
>
> Agreed. I actually examined these scenarios last week (independently as I
> found UrlScan and those settings myself), and then re-read what Kevin posted.
> I'd like confirmation as this directly contradicts what Kevin said. -- justin
Good point. In a hold pattern until someone else can confirm this.
-Fitz
Here's my patch in progress. If we get verification I'll commit it (with any needed changes):
Index: project_faq.html
===================================================================
--- project_faq.html (revision 9010)
+++ project_faq.html (working copy)
@@ -67,6 +67,9 @@
<p>
<strong>Troubleshooting:</strong>
</p>
+
+<li><a href="#vsnet">Subversion won't work with Microsoft VS.NET
+because of the <tt>.svn</tt> directories in my working copy.</a></li>
<li><a href="#wedged-repos">Every time I try to access
my repository, the process just hangs. Is my repository
corrupt?</a></li>
@@ -1048,6 +1051,31 @@
<![CDATA[-----------------------------------------------------------]]>
+<h3><a name="vsnet">Subversion won't work with Microsoft VS.NET
+because of the <tt>.svn</tt> directories in my working copy.</a></h3>
+
+<p>There seems to be a lot of confusion regarding VS.NET 200x and the
+".svn" directories. VS.NET has absolutely no problem with them. The
+"problem" is IIS6 which Microsoft patched to disallow paths containing
+dots (for "security reasons"). So waiting for the next release of
+VS.NET (Whidbey) won't do any good.</p>
+
+<p>Disallowing paths containing dots is only the <b><i>default</i></b>
+behaviour and can be easily worked around.</p>
+
+<p>The first thing to try is enabling parent path navigation:
+<a href="http://support.microsoft.com/?id=332117">http://support.microsoft.com/?id=332117</a></p>
+
+<p>If that doesn't work, then get <a
+href="http://www.microsoft.com/downloads/details.aspx?FamilyId=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en">UrlScan
+2.5</a> from Microsoft and configure it with <tt>AllowDotInPath=1</tt>
+in the ini-file.</p>
+
+<p><b>Never ever</b> use any of the two suggestions above in
+Internet-production environments.</p>
+
+<![CDATA[-----------------------------------------------------------]]>
+
<h3><a name="wedged-repos">Every time I try to access my repository, the
process just hangs. Is my repository corrupt?</a></h3>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: VS.NET and ".svn" is a *non-issue*
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
I'll try to take another look at this on Monday.
--
~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson
~~~~~~~~~~~~~~~~~~~~
> -----Original Message-----
> From: Justin Erenkrantz [mailto:justin@erenkrantz.com]
> Sent: Friday, March 12, 2004 9:28 AM
> To: Greg Hudson; Brian W. Fitzpatrick
> Cc: dev@subversion.tigris.org
> Subject: Re: VS.NET and ".svn" is a *non-issue*
>
> --On Friday, March 12, 2004 12:22 PM -0500 Greg Hudson <gh...@MIT.EDU>
> wrote:
>
> > On Fri, 2004-03-12 at 12:20, Brian W. Fitzpatrick wrote:
> >> Nick, thank you a million. I'm putting this into the FAQ right now!
> >
> > Um, minor problem: I don't think it's true.
>
> Agreed. I actually examined these scenarios last week (independently as I
> found UrlScan and those settings myself), and then re-read what Kevin
> posted.
> I'd like confirmation as this directly contradicts what Kevin said. --
> justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: VS.NET and ".svn" is a *non-issue*
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Friday, March 12, 2004 12:22 PM -0500 Greg Hudson <gh...@MIT.EDU> wrote:
> On Fri, 2004-03-12 at 12:20, Brian W. Fitzpatrick wrote:
>> Nick, thank you a million. I'm putting this into the FAQ right now!
>
> Um, minor problem: I don't think it's true.
Agreed. I actually examined these scenarios last week (independently as I
found UrlScan and those settings myself), and then re-read what Kevin posted.
I'd like confirmation as this directly contradicts what Kevin said. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: VS.NET and ".svn" is a *non-issue*
Posted by Greg Hudson <gh...@MIT.EDU>.
On Fri, 2004-03-12 at 12:20, Brian W. Fitzpatrick wrote:
> Nick, thank you a million. I'm putting this into the FAQ right now!
Um, minor problem: I don't think it's true.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: VS.NET and ".svn" is a *non-issue*
Posted by "Brian W. Fitzpatrick" <fi...@red-bean.com>.
Nick, thank you a million. I'm putting this into the FAQ right now!
-Fitz "Just the FAQs ma'am,"
On Thu, 2004-03-11 at 03:07, nick vajberg wrote:
> I see a lot of confusion regarding VS.NET 200x and the
> ".svn" directories. While I hate the .svn directories
> in general, VS.NET have absolutely no problem with
> them. Read along.
>
> The "problem" is IIS6 which M$ patched to disallow
> paths containing dots and they did so for security
> reasons (...oh my, what a hack). So waiting for
> Whidbey won't do any good.
>
> Now, this is only the DEFAULT behaviour and can be
> easily worked around (as with other M$ security
> patches ;-)
>
> The first thing to try is enabling parent path
> navigation:
> http://support.microsoft.com/?id=332117
>
> If that doesn't work, then get UrlScan 2.5 from
> Microsoft and configure it with AllowDotInPath=1 in
> the ini-file.
>
> UrlScan is here:
> (http://www.microsoft.com/downloads/details.aspx?FamilyId=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en)
>
> NEVER EVER use any of the two suggestions above in
> Internet-production environments.
>
> That said, I hope Subversion will someday have
> something better than the .svn directories. They are
> eating my hard drive and driving my tools nuts.
>
> My suggestions is: Do NOT add support for "_svn". Some
> tools will probably have problem with those too.
> Rather, focus on replacing the entire .svn scheme with
> something less insane.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: VS.NET and ".svn" is a *non-issue*
Posted by "Daniel L. Rall" <dl...@collab.net>.
Yes, let that be the end of it. Slight correction on "the best course", which
should be to document the work around in the book -- there will be plenty of
VS.Net + IIS6 users.
kfogel@collab.net wrote:
> Thanks, Nick. IMHO, that's the end of it. Since there's a
> workaround, albeit an insecure one, our best course is to do nothing.
>
> (This is unrelated to possible future replacements of .svn/ with
> something else, of course; that's not driven by the IIS6 bug.)
>
> -Karl
>
> nick vajberg <ni...@yahoo.dk> writes:
>
>>I see a lot of confusion regarding VS.NET 200x and the
>>".svn" directories. While I hate the .svn directories
>>in general, VS.NET have absolutely no problem with
>>them. Read along.
>>
>>The "problem" is IIS6 which M$ patched to disallow
>>paths containing dots and they did so for security
>>reasons (...oh my, what a hack). So waiting for
>>Whidbey won't do any good.
>>
>>Now, this is only the DEFAULT behaviour and can be
>>easily worked around (as with other M$ security
>>patches ;-)
>>
>>The first thing to try is enabling parent path
>>navigation:
>>http://support.microsoft.com/?id=332117
>>
>>If that doesn't work, then get UrlScan 2.5 from
>>Microsoft and configure it with AllowDotInPath=1 in
>>the ini-file.
>>
>>UrlScan is here:
>>(http://www.microsoft.com/downloads/details.aspx?FamilyId=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en)
>>
>>NEVER EVER use any of the two suggestions above in
>>Internet-production environments.
>>
>>That said, I hope Subversion will someday have
>>something better than the .svn directories. They are
>>eating my hard drive and driving my tools nuts.
>>
>>My suggestions is: Do NOT add support for "_svn". Some
>>tools will probably have problem with those too.
>>Rather, focus on replacing the entire .svn scheme with
>>something less insane.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: VS.NET and ".svn" is a *non-issue*
Posted by kf...@collab.net.
Thanks, Nick. IMHO, that's the end of it. Since there's a
workaround, albeit an insecure one, our best course is to do nothing.
(This is unrelated to possible future replacements of .svn/ with
something else, of course; that's not driven by the IIS6 bug.)
-Karl
nick vajberg <ni...@yahoo.dk> writes:
> I see a lot of confusion regarding VS.NET 200x and the
> ".svn" directories. While I hate the .svn directories
> in general, VS.NET have absolutely no problem with
> them. Read along.
>
> The "problem" is IIS6 which M$ patched to disallow
> paths containing dots and they did so for security
> reasons (...oh my, what a hack). So waiting for
> Whidbey won't do any good.
>
> Now, this is only the DEFAULT behaviour and can be
> easily worked around (as with other M$ security
> patches ;-)
>
> The first thing to try is enabling parent path
> navigation:
> http://support.microsoft.com/?id=332117
>
> If that doesn't work, then get UrlScan 2.5 from
> Microsoft and configure it with AllowDotInPath=1 in
> the ini-file.
>
> UrlScan is here:
> (http://www.microsoft.com/downloads/details.aspx?FamilyId=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en)
>
> NEVER EVER use any of the two suggestions above in
> Internet-production environments.
>
> That said, I hope Subversion will someday have
> something better than the .svn directories. They are
> eating my hard drive and driving my tools nuts.
>
> My suggestions is: Do NOT add support for "_svn". Some
> tools will probably have problem with those too.
> Rather, focus on replacing the entire .svn scheme with
> something less insane.
>
> Thanks.
>
> Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org