-1

I migrated some subversion repositories to a new server with Apache 2.4 and Subversion 1.8.10. The most repositories have only a basic user authentication and it works. But one repository needs a IP based authentication for read access and a basic authentication for committing changes. I activate the compatibility module for the old syntax. I don't know that subversion is full compatible with Apache 2.4.

Apache2 Config

<Location /svn/repo>
 SSLRequireSSL
 DAV svn
 SVNPath /path/to/svn/repo
 AuthzSVNAccessFile /path/to/authz/svnaccessfile
 Satisfy Any
 Require valid-user
 AuthType Basic
 AuthName "Auth"
 AuthUserFile /path/to/passwd
 Include /file/of/some/other/allowed/ips
 Order allow,deny
 Allow from 1.1.1.1 134.76.28
 Deny from all 
 </Location>

svnaccessfile

# defining groups
[groups]
repo=james,tim
[repo:/]
@repo = rw
* = r

If I test this configuration, the repos is available, it's only available by basic auth or IP. On first the look everything is ok. But if anybody want to commit to the repository with an allowed IP, he can commit without login.

svn log

svn log
------------------------------------------------------------------------
r173 | (kein Autor) | 2019-02-12 12:20:45 +0100 (Di, 12. Feb 2019) | 1 Zeile

I also read that the following LimitExcept should solve this problem but no change on anonymous commit.

<LimitExcept GET PROPFIND OPTIONS REPORT>
 Require valid-user
</LimitExcept>

Can't handle Satisfy Any this problem or how can I use based auth and ip based auth with subversion?

  • I found the problem. It's not possible to use successfully the new syntax in Apache 2.4 with subversion. The included file was generated with require ip 1.1.1.1. – B3nny Feb 18 at 8:37

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.