bug fix: perms propagation to slaves...
Sometime after v3.2, I fixed what looked like an information disclosure issue, where a user could determine if an arbitrary repo existed or not, even if he had no rights to see the repo. This was:96cc2ea
"new features relating to creating wild repos:" Unfortunately, this appears to have broken gl-perms propagation to slaves, because now running "perm -c" on an existing repo dies! If you run git diff96cc2ea
^ <this commit> -- src/commands/perms you'll see how simple the fix *should* have been :-(
This commit is contained in:
parent
b303694882
commit
84424e48b9
2 changed files with 13 additions and 13 deletions
|
@ -100,7 +100,7 @@ try "
|
|||
# auto-create using perms fail
|
||||
echo READERS u5 | glt perms u4 -c foo/u4/baz
|
||||
!/Initialized empty Git repository in .*/foo/u4/baz.git/
|
||||
/FATAL: repo already exists or you are not authorised to create it/
|
||||
/FATAL: repo does not exist, or you are not authorised/
|
||||
|
||||
# auto-create using perms
|
||||
echo READERS u2 | glt perms u1 -c foo/u1/baz
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue