Hello! I maintain ejabberd and I've got an issue filed about ejabberd's policykit policy being desktop-centric[0]. I've done some reading about how I could alter the policy to make it so that it doesn't expect the user to be at a seat, but I can't help but think that sudo is a great way to handle this problem and probably is what a server admin would expect to use to control access to ejabberdctl. I'm leaning towards removing the policykit integration from ejabberd, but I wanted to ask on this list if there's a reason I should keep and maintain it. I honestly don't know much about it, so if there's a value in it that I'm not seeing I'd love to be educated. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1094143
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
