Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#902 Inconsistent permissions (@all deny enter is not enough))

1.2.3
open
nobody
None
5
2012-12-09
2012-08-07
Natenom
No

If you deny "enter" permission to all in a channel nobody can enter it.
But if a user has inherited "move" permission, he is still able to enter the channel
until you additionally add for example the following ACL entry:
a) @all deny move
or
b) @all deny traverse

Now everyone is denied to enter the channel.

How to reproduce:
1. Create a new channel.
2. In ACL-Editor disable inheritance.
3. Add following entries:
- @all allow move
- @all deny enter

If you hit enter, your Mumble client will automatically add an entry "@yourname allow write ACL", which is ok.

Now everyone is able to join the channel until you add entry a or b (see above).

In fact, a user with "deny enter", but "allow move" is able to join a channel dragging himself into it,
but this is a different permission and should not interfere with enter permission.

This "works" with the current git version and with 1.2.3.

Discussion

  • Kissaki
    Kissaki
    2012-12-09

    • milestone: --> 1.2.3