[Date Prev][Date Next] [Chronological] [Thread] [Top]

drop Cyrus 1.5 support

Given that Cyrus 2.1 has been around for quite a while now, and 1.5 has been
unmaintained for more than a year, I think it would be a good idea to drop
the 1.5 support from our code. At this point I only see it being a source of
unnecessary hassles (see ITS#2484 and ITS#2694 for currently known problems
due to using Cyrus 1.5.27).

Whether we change this in 2.1 (and how) is open in my mind, but we should
probably eliminate all traces of Cyrus 1.5 support in the OpenLDAP 2.2 code.


  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Monday, September 15, 2003 2:21 PM
To: Howard Chu
Subject: RE: re21 CHANGES

At 12:48 PM 9/15/2003, Howard Chu wrote:
>> -----Original Message-----
>> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>> At 12:31 PM 9/15/2003, Howard Chu wrote:
>> >What do you think of merging these:
>> >
>> >Modified Files:
>> >        cyrus.c  1.89 -> 1.90
>> >
>> >Log Message:
>> >ITS#2484, set sasl_maxbuf to SASL_MAX_BUFF_SIZE if it was negotiated
>> >as zero.
>> Seems odd to me.  Wouldn't that lead to layers being installed
>> with the buffer length was negotiated to be zero (and hence off)?
>Maybe the better solution is to withdraw support for Cyrus SASL 1.5.

Okay by me.  But maybe we should discuss this on -devel first.

> ITS#2694
>(Second instance of slapd segfaults) is also occurring on a Cyrus 1.5.27