Marcus Rueckert wrote:
> On 2006-05-31 16:30:13 +0300, Vlad Georgescu wrote:
>> I changed the build system to handle passing --with-sasl[=PATH] to
>> Update the build system on *nix to support Cyrus SASL.
>> * build/ac-macros/sasl.m4: New file.
>> * configure.in: Call SVN_SASL_LIB.
>> * Makefile.in
>> (SVN_SASL_LIBS, SVN_SASL_INCLUDES): New AC_SUBSTed variables.
>> Add SVN_SASL_INCLUDES to INCLUDES.
>> * aclocal.m4
>> Add build/ac-macros/sasl.m4 to the list of supplementary macros.
>> * build.conf
>> (sasl): New entry.
>> (libsvn_ra_svn, svnserve): Add sasl to the list of dependencies.
>> Any comments would be appreciated.
> will you support dovecot sasl on the server side?
Whilst that might be an interesting idea for the future, I support
Vlad's scoping of his SoC proposal to getting good SASL support working
with just one specific SASL library implementation (Cyrus).
> configuring postfix for dovecot sasl is much easier.
> timo is relicensing the sasl code as bsd. (process is running atm)
Glancing briefly at postfix, it looks like they are using a custom
reimplementation of code to talk to the dovecot auth daemon. Whilst the
Dovecot SASL implementation does, as far as I'm aware, have a reputation
for quality, it is still undergoing the process of transitioning from an
integral part of dovecot itself, to a deliberately re-usable library. As
such, I think we should definitely devote attention to it, but it
doesn't seem like an ideal basis on which to build our initial SASL
Received on Wed May 31 18:40:06 2006