[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pysieved] Dovecot auth/userdb files for pysieved
- From: Koen Vermeer <koen at vermeer dot tv>
- Subject: Re: [pysieved] Dovecot auth/userdb files for pysieved
- Date: Wed, 02 May 2007 08:49:03 +0200
Hi Neale,
Op di, 01-05-2007 te 21:58 -0600, schreef Neale Pickett:
> In your patch, you contact two different sockets for authentication and
> userdb. Is it possible to get all information with a single request to a
> single socket? If so, I will rework pysieved's plugin system so that it only
> has to ask once. Otherwise, I can postpone making this big change until
> something else requires it :)
Let me start by saying that I hope your daughter is well, or, at least,
that things are heading in the right direction.
Dovecot has two sockets. One is for authentication only, the other for
getting uid, gid, home directory etc. The first one generally doesn't
require any special privileges, while the second one does. I assume that
the second one could be used for both auth and userdb, but that does
mean that pysieved would have to run as root (or some other special
user) in all (Dovecot) cases.
I could probably hack something together that uses the high-security
socket for all communication if it can access it, and only the
low-security socket for authentication if the high-security one isn't
specified.
Regarding the plugin system: It would be more flexible if a module would
be allowed to fill in as many of the yet unknown fields as possible. The
main program could then check if all required data is known. If not, it
should call the appropriate plugin to get more details. I haven't really
thought this through, though, so it might be just a dumb idea.
Let me know what you prefer with the sockets.
Koen