Re: SVN access denied when comparing revisions
Bill Cebula bill.ceb...@gmail.com writes: If that information ( Lack of explicit anon-access is interpreted as anon-access=read) was in the svnserv.conf file, it would have saved me a few hours of troubleshooting. Subversion 1.7 (but not 1.6) creates svnserv.conf with the following: ### The sample settings below are the defaults and specify that anonymous ### users have read-only access to the repository, while authenticated ### users have read and write access to the repository. # anon-access = read # auth-access = write -- Certified Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
Re: SVN access denied when comparing revisions
Philip Martin wrote: Subversion 1.7 (but not 1.6) creates svnserv.conf with the following: ### The sample settings below are the defaults and specify that anonymous ### users have read-only access to the repository, while authenticated ### users have read and write access to the repository. # anon-access = read # auth-access = write The exact text may have changed, but something like this has been included in the default svnserve.conf for quite a while; here's the segment from a repo I've had in its current form since at least ~SVN 1.5 (due to dump/reload to move to a new machine), possibly as far back as 1.2: [general] ### These options control access to the repository for unauthenticated ### and authenticated users. Valid values are write, read, ### and none. The sample settings below are the defaults. # anon-access = read # auth-access = write (TBH I'm not sure why it was changed, it's perfectly clear to *me*...) I just created a new repo with 1.6.15 to see what it did, and it produced exactly the same as just above. -kgd
Re: SVN access denied when comparing revisions
Kris Deugau wrote on Fri, Mar 22, 2013 at 10:41:27 -0400: Philip Martin wrote: Subversion 1.7 (but not 1.6) creates svnserv.conf with the following: ### The sample settings below are the defaults and specify that anonymous ### users have read-only access to the repository, while authenticated ### users have read and write access to the repository. # anon-access = read # auth-access = write The exact text may have changed, but something like this has been included in the default svnserve.conf for quite a while; here's the segment from a repo I've had in its current form since at least ~SVN 1.5 (due to dump/reload to move to a new machine), possibly as far back as 1.2: [general] ### These options control access to the repository for unauthenticated ### and authenticated users. Valid values are write, read, ### and none. The sample settings below are the defaults. # anon-access = read # auth-access = write (TBH I'm not sure why it was changed, it's perfectly clear to *me*...) You don't say what's unclear about the new text. Currently trunk generates this (1.7 does something similar): [general] ### The anon-access and auth-access options control access to the ### repository for unauthenticated (a.k.a. anonymous) users and ### authenticated users, respectively. ### Valid values are write, read, and none. ### Setting the value to none prohibits both reading and writing; ### read allows read-only access, and write allows complete ### read/write access to the repository. ### The sample settings below are the defaults and specify that anonymous ### users have read-only access to the repository, while authenticated ### users have read and write access to the repository. # anon-access = read # auth-access = write
Re: SVN access denied when comparing revisions
Daniel Shahaf wrote: Kris Deugau wrote on Fri, Mar 22, 2013 at 10:41:27 -0400: (TBH I'm not sure why it was changed, it's perfectly clear to *me*...) You don't say what's unclear about the new text. I don't see much difference between them at all - obviously others did, and felt that the older text was less clear. -kgd
Re: SVN access denied when comparing revisions
Phillip, Thanks for the reply. If the line anon-access = read is commented out, can't that be interpreted as anon-access = none on startup of the server? It seems like a 1 line conditional statement is all that is needed to fix this particular issue. I realize it is related to a larger bug. Thanks, Bill On Wed, Mar 20, 2013 at 6:41 AM, Philip Martin philip.mar...@wandisco.comwrote: Bill Cebula bill.ceb...@gmail.com writes: I would expect the same behavior whether the* anon-access* line is commented or whether it is specified as *none*. However, if the anon-access line is commented, you get the error even though you the* authz* specifies read/write privileges for the entire repository. This is a known bug. The svn:// protocol chooses either anonymous or authenticated access right at the start of the connection and has no way to upgrade later. http://subversion.tigris.org/issues/show_bug.cgi?id=2712 -- Certified Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
Re: SVN access denied when comparing revisions
Bill Cebula wrote on Thu, Mar 21, 2013 at 18:30:23 -0500: Phillip, Thanks for the reply. If the line anon-access = read is commented out, can't that be interpreted as anon-access = none on startup of the server? No, lack of explicit anon-access is interpreted as anon-access=read. (and that can't be changed for compatibility reasons) Daniel It seems like a 1 line conditional statement is all that is needed to fix this particular issue. I realize it is related to a larger bug. Thanks, Bill On Wed, Mar 20, 2013 at 6:41 AM, Philip Martin philip.mar...@wandisco.comwrote: Bill Cebula bill.ceb...@gmail.com writes: I would expect the same behavior whether the* anon-access* line is commented or whether it is specified as *none*. However, if the anon-access line is commented, you get the error even though you the* authz* specifies read/write privileges for the entire repository. This is a known bug. The svn:// protocol chooses either anonymous or authenticated access right at the start of the connection and has no way to upgrade later. http://subversion.tigris.org/issues/show_bug.cgi?id=2712 -- Certified Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
Re: SVN access denied when comparing revisions
If that information ( Lack of explicit anon-access is interpreted as anon-access=read) was in the svnserv.conf file, it would have saved me a few hours of troubleshooting. Thanks, Bill On Thu, Mar 21, 2013 at 7:31 PM, Daniel Shahaf d...@daniel.shahaf.namewrote: Bill Cebula wrote on Thu, Mar 21, 2013 at 18:30:23 -0500: Phillip, Thanks for the reply. If the line anon-access = read is commented out, can't that be interpreted as anon-access = none on startup of the server? No, lack of explicit anon-access is interpreted as anon-access=read. (and that can't be changed for compatibility reasons) Daniel It seems like a 1 line conditional statement is all that is needed to fix this particular issue. I realize it is related to a larger bug. Thanks, Bill On Wed, Mar 20, 2013 at 6:41 AM, Philip Martin philip.mar...@wandisco.comwrote: Bill Cebula bill.ceb...@gmail.com writes: I would expect the same behavior whether the* anon-access* line is commented or whether it is specified as *none*. However, if the anon-access line is commented, you get the error even though you the* authz* specifies read/write privileges for the entire repository. This is a known bug. The svn:// protocol chooses either anonymous or authenticated access right at the start of the connection and has no way to upgrade later. http://subversion.tigris.org/issues/show_bug.cgi?id=2712 -- Certified Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
Re: SVN access denied when comparing revisions
Bill Cebula bill.ceb...@gmail.com writes: I would expect the same behavior whether the* anon-access* line is commented or whether it is specified as *none*. However, if the anon-access line is commented, you get the error even though you the* authz* specifies read/write privileges for the entire repository. This is a known bug. The svn:// protocol chooses either anonymous or authenticated access right at the start of the connection and has no way to upgrade later. http://subversion.tigris.org/issues/show_bug.cgi?id=2712 -- Certified Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
