Jeremy Howard wrote:
>
> Ken Murchison wrote:
> > Christopher Audley wrote:
> <...>
> > >
> > > Because the protocol is essentially the same as pwcheck, you can lift
> > > saslauthd from a latter version of SASL and use it with your 1.5.24 SASL
> > > installation.
> >
> > Well... This is *most likely* going to change in SASL v2. The current
> > thinking between myself, Lyndon Nerenberg from Messaging Direct (the
> > original author of saslauthd), and Rob Siemborski and Larry Greenfield
> > from CMU, is that the protocol will be changed to use counted length
> > strings instead of NUL delimited strings, and will be extended to
> > include the service name and user realm. An example from Lyndon is
> > below.
> >
> Why the proposed change, Ken? The current null termination is easy to use
> and existing daemons already work with it.
Now that I think about it, what's the difference? The pwcheck
capability is not going away, so anything you have already written will
still work. With saslauthd, the daemon itself speaks the protocol, NOT
the backend mechanism. As long as the API for mechanisms doesn't change
(which it will/has in the SASL v2 code), we should be able to change the
protocol all day long without breaking the "plug-in" code.
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
