On Thu, 30 Oct 2003, Craig Ringer wrote: > I'd really appreciate feedback on this - what have I missed, do I have > anything just plain wrong, etc. I've left out some things - like the > 'shadow' mechanism of saslauthd - that seem best solved using other > methods (getpwent in that case). Also left out are the specific-vendor > mechanisms like saslauthd's dce and sia methods.
You've totally missed the mechanism layer -- the authentication mechanisms such as PLAIN, DIGEST-MD5, KERBEROS_V4, GSSAPI and so on, which are pretty key in understanding how things fit together. SASL is really three layers: application, framework, and mechanism. Cyrus SASL has the added auxprop/saslauthd "layer" which is used by various mechanisms. > I should probably also include rimap. Is this best done via saslauthd? It is only done via saslauthd. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper