Bug 135095
Summary: | LDAP support missing from cyrus-sasl | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Graham Leggett <minfrin> |
Component: | cyrus-sasl | Assignee: | Steve Conklin <sconklin> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:16:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Graham Leggett
2004-10-08 16:28:52 UTC
I do not understand, why it's not LDAP enabled by default, here is a workaround, rebuild package using fix below, proper working now here on my system. Note also that version cyrus-sasl-2.1.19-5.EL4 of RHEL4 is LDAP enabled by default. --- cyrus-sasl-2.1.15-10.spec 2005-02-21 20:13:48.000000000 -0500 +++ cyrus-sasl-2.1.15-10.1.spec 2005-02-21 21:16:54.000000000 -0500 @@ -5,7 +5,7 @@ Summary: The Cyrus SASL library. Name: cyrus-sasl Version: 2.1.15 -Release: 10 +Release: 10.1 License: Freely Distributable Group: System Environment/Libraries Source0: ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-sasl-%{version}.tar.gz @@ -176,6 +176,7 @@ --enable-cram \ --enable-digest \ --enable-plain \ + --with-ldap=/usr/include \ --enable-login # --enable-auth-sasldb -- EXPERIMENTAL make sasldir=%{_plugindir2} This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |