About Cyrus SASL documentation depth

[Patrick Ben Koetter]

There are, I think, three major aspects to Cyrus SASL documentation:

1. How Cyrus SASL basically works (Discussion of mechanisms, methods, etc.)
2. How Cyrus SASL must be configured to get XYZ.
3. How other applications must be configured to have Cyrus SASL work. I am not
   thinking of e.g. how to configure Postfix to offer SMTP AUTH. What I have
   on mind is: How must e.g. OpenLDAP be configured to have the ldapdb auxprop
   plugin work for other apps. This involves some major configuration, which I
   consider to be more part of OpenLDAP. Should we leave such documentation to
   the other maintainer teams or should we go all the way?

Which of the aspects should our documentation cover? I think it should be (2)
and (3) and maybe some parts of (1) - in as much as their understanding is
required to get (2) and (3).


And...
anyone familiar with KERBEROS? I haven't done a Kerberos installation and
configuration and I wil probably need some help setting it up before I can
write about it. ;)

p at rick



-- 
The Book of Postfix
<http://www.postfix-book.com>
saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>