Tarjei Huse wrote:
> Would it be possible to host a cyrus-(IMAP/SASL) documetnation page? I
feel
> a great need for a Cyrus faq/howto page. The current doc's are not exactly
> in a perfect state.
>
> Also, they could bennefit a lot from dynamic updates.
>
Agreed!

> Does anyone have a suggestion on where and how this could be done?
>
I'd suggest hosting a project on Sourceforge. For an example of how others
are using Sourceforge to host dynamic documentation sites, check out:
  http://vim.sourceforge.net/tips/

As to how to get this done, just volunteer and start writing! Information on
setting up a Sourceforge project is available at http://www.sf.net

It would be nice if Cyrus IMAPd itself was hosted on Sourceforge--any such
plans?

> Also, as a sidenote, a pollsystem should be made:
> What do you want as auth system?
> * SASL w/ LDAP support
> * C-IMAP w/ LDAP support
> * C- IMAP w/ PAM support
> * Reentrant SASL?
>
> Seriously, I think a large part of this discussion is a question of how to
> support mysql and ldap based auth systems. I think these are quite valid
> needs of functionality for an auth system and should be included as
options
> for authentication either in sasl og directly in cyrus.
>
I don't think this is necessary. Under SASL v2 this problem goes away
(indeed in 1.5.27 it goes away using saslauthd). Replacing SASL which is
designed for secure, network-aware authentication, with PAM which is
designed for _interactive_ authentication (but can be hacked around for
silent authentication, although not for secure protocols like krb5), is not
an option.

Anyway, there's currently a flexible solution in the form of pwcheck.

The problem with the current situation is that:
 1- pwcheck is not widely understood
 2- pwcheck is not well documented
 3- there is no central repository of pwcheck daemons

The recent discussions about LDAP hopefully has raised the awareness of
pwcheck. 2 & 3 should be sorted out by the pwcheck repository that I'm
setting up on Sourceforge at the moment, where I'll also put pwcheck
documentation if I (or someone else) gets around to writing it.


Reply via email to