On Sat, 2008-10-11 at 00:05 -0700, Ian R. Justman wrote: > Hi, all. > > I have successfully deployed the code I wrote to handle Post.Office > password hashes. However, I had to implement it as a hack to > password-scheme.c. I'd like to implement it as a module so I don't have > to hack Dovecot whenever a new release comes out. However, I had a few > thoughts: > > 1. I used Dovecot's own MD5 routines in my implementation because I > know how they behave. However, would it make sense to distribute the C > sources for the MD5 routines, or would it make far more sense to have a > Dovecot build tree already (so I can use Dovecot's function library)?
If you're using the public MD5 functions from md5.h, you don't need a build tree. You'll just need the md5.h. And you'll need password-scheme.h in any case. Those headers can be installed and some distributions have them in dovecot-devel package. > 2. Is there good documentation for Dovecot's plugin API? I need it so > I can figure out how to write the parts which the main program call so > then the code can be used as a plugin. The plugin API is really simple. At startup it calls <plugin_name>_init() and at exit it calls <plugin_name>_deinit(). Inside those functions you can do anything the main program could do.
signature.asc
Description: This is a digitally signed message part
