On Wed, Jan 24, 2018 at 11:05:40AM +0100, Torsten Krah wrote:
> Some more news about that, debugged that a little bit further and imho i
> think its a bug in the module code of access_checker - or there are
> assumptions made which do not hold in my usecase - at least its unclear
> to me why its do
Some more news about that, debugged that a little bit further and imho i
think its a bug in the module code of access_checker - or there are
assumptions made which do not hold in my usecase - at least its unclear
to me why its done that way, maybe someone can give some input.
The problem is that t
Am Montag, den 22.01.2018, 13:12 +0100 schrieb Torsten Krah:
> Good catch, but this does not explain the first example of the OP:
>
>[repo:/]
>myuser = rw
> - The client (curl) shows me the repo-root but none of the files below.
> - The error_log shows, that my user got authorize
Good catch, but this does not explain the first example of the OP:
[repo:/]
myuser = rw
- The client (curl) shows me the repo-root but none of the files below.
- The error_log shows, that my user got authorized on root:
[Fri Jan 19 21:20:58.735108 2018] [authz_svn:info] [pid 3465:
On Mon, Jan 22, 2018 at 11:39:26AM +, Stefan Hauffe wrote:
> Hello,
>
> I refined my mail from 05/01/2017 and now I think there is a bug in the
> mod_authz_svn Module. This may allow users to see content for which they
> aren't allowed for.
>
> For the general setup, I have an Apache 2.4, S
Hello,
I refined my mail from 05/01/2017 and now I think there is a bug in the
mod_authz_svn Module. This may allow users to see content for which they aren't
allowed for.
For the general setup, I have an Apache 2.4, Subversion 1.9 modules and mod_lua
activated for authentification. The LUA-ho
