Re: Summary/Confirmation - RedHat sasl libraries don't work with 2.2.x
Joe Rhett schrieb: I'd like to note for the record (and anyone else searching) that the sasl that ships with Redhat WILL NOT work with 2.2.1. It returns OK with an empty realm. For unknown reasons, Cyrus then returns an Login failed: can't request info until later in exchange I'm not sure why Cyrus 2.2.1 is unhappy with the OK response, but it is. IIRC this is only the case when authenticating using saslauthd, not when using sasldb. Simon As per the only thread I could find on this subject, upgrading to sasl 2.1.15 solved the problem. I left the Redhat plugins and saslauthd in place, just replaced the shared library and it works. So Rob's suggestion was correct. (Sorry, can't find the original thread handy) Can someone with a RedHat contract persuade them to provide updates from 2.1.10-3 to 2.1.15 ? As stated above, I'm just reaffirming this for other searchers. When I'm searching for solutions to problems, I always appreciate finding confirmation that a problem was replicable. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
Re: Summary/Confirmation - RedHat sasl libraries don't work with 2.2.x
Sorry, you are right -- I failed to qualify that. On Wed, Oct 01, 2003 at 08:50:00AM +0200, Simon Matter wrote: Joe Rhett schrieb: I'd like to note for the record (and anyone else searching) that the sasl that ships with Redhat WILL NOT work with 2.2.1. It returns OK with an empty realm. For unknown reasons, Cyrus then returns an Login failed: can't request info until later in exchange I'm not sure why Cyrus 2.2.1 is unhappy with the OK response, but it is. IIRC this is only the case when authenticating using saslauthd, not when using sasldb. Simon As per the only thread I could find on this subject, upgrading to sasl 2.1.15 solved the problem. I left the Redhat plugins and saslauthd in place, just replaced the shared library and it works. So Rob's suggestion was correct. (Sorry, can't find the original thread handy) Can someone with a RedHat contract persuade them to provide updates from 2.1.10-3 to 2.1.15 ? As stated above, I'm just reaffirming this for other searchers. When I'm searching for solutions to problems, I always appreciate finding confirmation that a problem was replicable. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
Summary/Confirmation - RedHat sasl libraries don't work with 2.2.x
I'd like to note for the record (and anyone else searching) that the sasl that ships with Redhat WILL NOT work with 2.2.1. It returns OK with an empty realm. For unknown reasons, Cyrus then returns an Login failed: can't request info until later in exchange I'm not sure why Cyrus 2.2.1 is unhappy with the OK response, but it is. As per the only thread I could find on this subject, upgrading to sasl 2.1.15 solved the problem. I left the Redhat plugins and saslauthd in place, just replaced the shared library and it works. So Rob's suggestion was correct. (Sorry, can't find the original thread handy) Can someone with a RedHat contract persuade them to provide updates from 2.1.10-3 to 2.1.15 ? As stated above, I'm just reaffirming this for other searchers. When I'm searching for solutions to problems, I always appreciate finding confirmation that a problem was replicable. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
