[Dovecot] ACLs: Group ACL adds empty ACL for user of same name, why?
I'm playing around with ACLs, Groups and SOGo on Debian Stable, Dovecot 1.2.15.
If I set an ACL for a group 'developers':
6 setacl "INBOX.Trash" "$developers" "lrsw" 6 OK Setacl complete.
The dovecot-acl file for INBOX.Trash then contains a group setting for the group, and a user setting for a user of the same name, giving it no permissions.
group=developers lrws user=developers
and a subsequent GETACL reports the user:
5 getacl "INBOX.Trash"
- ACL "INBOX.Trash" "$developers" lrws "developers" "" "jim" lrwstipekxacd 5 OK Getacl completed.
Currently SOGo does not deal well with the unexpected non-existant user. So I'm curious - why's it there?
Jim Hague - jim.hague@acm.org Never trust a computer you can't lift.
On Mon, 2011-06-27 at 14:40 +0100, Jim Hague wrote:
I'm playing around with ACLs, Groups and SOGo on Debian Stable, Dovecot 1.2.15.
If I set an ACL for a group 'developers':
6 setacl "INBOX.Trash" "$developers" "lrsw" 6 OK Setacl complete.
The dovecot-acl file for INBOX.Trash then contains a group setting for the group, and a user setting for a user of the same name, giving it no permissions.
group=developers lrws user=developers
Looks like a bug. I see it's fixed in v2.0 already. You can't get it fixed to Debian stable .deb anyway, so I don't think there's much point in trying to backport the fix.
On Tuesday 28 Jun 2011 00:55:02 Timo Sirainen wrote:
On Mon, 2011-06-27 at 14:40 +0100, Jim Hague wrote:
If I set an ACL for a group 'developers' [...] The dovecot-acl file for INBOX.Trash then contains a group setting for the group, and a user setting for a user of the same name, giving it no permissions.
Looks like a bug. I see it's fixed in v2.0 already. You can't get it fixed to Debian stable .deb anyway, so I don't think there's much point in trying to backport the fix.
Thanks very much. I was worried that there was something subtle I'd missed; I was hoping it would turn out to be a Plain Old Bug.
You're right about Squeeze. I'll start looking at 2.0 and backports.
Jim Hague - jim.hague@acm.org Never trust a computer you can't lift.
participants (2)
-
Jim Hague
-
Timo Sirainen