Advice about SASL socket directory permissions

[UlisesVitulli]

Helo team!

Rene and I are planning to upload a SASL back-end authentication module
for Apache 2.2[1], here is the software in matter[2].

The reason of this mail is to ask you for advice about what we should
do/say to do, in reference to the directory permissions where saslauthd
places its socket on Debian system (var/run/saslauthd), as because of it
(0710) does not allow Apache running user (commonly www-data), to talk with.

We have arrived at this different 3 'solution' approaches:

1. Tell to add apache running user to sasl group.
2. Tell to change owner of the directory where saslauthd places its
socket (defaulted to var/run/saslauthd)
3. Tell to change permissions of the directory where saslauthd places
its socket (defaulted to var/run/saslauthd) to allow others with
+execution (ugly).


Hoping we could help each other, thanks in advance!



Dererk

ref
1.  #499186
2.  http://mod-authn-sasl.sourceforge.net/

-- 
vlady <at> Melee: ~$ grep -ir 'power in your hands' /proc/
/proc/version: Debian GNUine Perception

BOFH excuse #356: the daemons! the daemons! the terrible daemons!.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20081128/71152c4d/attachment.pgp