Re: [Cooker] sasl v2

2002-10-27 Thread Florin
[EMAIL PROTECTED] (Brian J. Murrell) writes:

 --9UV9rz0O2dU/yYYn
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 When will Mandrake be upgrading all of their uses of sasl v1 to v2?
 It is becoming more and more difficult to support a mixed enviroment
 of sasl v1 and v2 as they are not re-entrant.  When you have an
 application chain that involved both v1 and v2, they pollute each
 other's data space.
 
 The quintessential example is trying to use Cyrus IMAPD (which
 requires sasl v2) with LDAP (which is linked with sasl v1) on Mandrake
 Linux.  It just does not work because of the re-entrancy problems.
 
 It is worth noting that sasl v1 is no longer being developed and all
 new work is going into v2.
 
 b.

Howdi,

I'm the new maintainer of the cyrus-sasl packages and I'll have a look
next week to what need to be done updates/fixes etc ... any constructive
ideas are welcomed. 

Feel free to mail me directly, if it doesn't concern the cooker ml ...

cheers,
-- 
Florin  http://www.mandrakesoft.com
http://people.mandrakesoft.com/~florin/




[Cooker] sasl v2

2002-10-26 Thread Brian J. Murrell
When will Mandrake be upgrading all of their uses of sasl v1 to v2?
It is becoming more and more difficult to support a mixed enviroment
of sasl v1 and v2 as they are not re-entrant.  When you have an
application chain that involved both v1 and v2, they pollute each
other's data space.

The quintessential example is trying to use Cyrus IMAPD (which
requires sasl v2) with LDAP (which is linked with sasl v1) on Mandrake
Linux.  It just does not work because of the re-entrancy problems.

It is worth noting that sasl v1 is no longer being developed and all
new work is going into v2.

b.

-- 
Brian J. Murrell



msg79990/pgp0.pgp
Description: PGP signature