--On Wednesday, January 29, 2014 10:59:38 AM -0500 "Roberto C. Sánchez"
<[email protected]> wrote:
On Sun, Mar 24, 2013 at 11:17:22AM -0700, Bill MacAllister wrote:
And after doing some more testing, with the correct server this time,
I discovered that 2.1.26 does _not_ fix the problem, i.e. minssf=1
needs to be specified in the OpenLDAP configuration element
olcSaslSecProps. Sorry for the mis-direction.
And, thinking about this some more it is not clear that this is a bug
in Cyrus SASL. At a minimum JNDI should give a better error message
than it is, but really JNDI should just probably handle it.
Hi Bill,
I am going through the bugs against cyrus-sasl2 and I see that this bug
has not seen activity since the initial flurry last year. Is there a
verdict on whether this bug really is in Cyrus SASL or does the bug
reside elsewhere? If it is in Cyrus SASL, do you have a recommendation
on how we ought to proceed, or do we leave it to upstream?
Regards,
-Roberto
Hi,
While this is a change in behaviour in cyrus-sasl2 I don't think that
it is a bug in cyrus-sasl2. Do I need to close the bug or can you do
that for me?
Bill
--
Bill MacAllister
Infrastructure Delivery Group, Stanford University
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
