Description of problem: I'm trying to compile mod_auth_krb5-rc3 on RedHat AS 2.1 as a dso. I have installed the following krb5-packages: krb5-libs-1.2.2-13 krb5-devel-1.2.2-13 krb5-workstation-1.2.2-13 When I start "./configure --with-krb5=/usr/kerberos --with- apache=/opt/apache2 --without-krb4" I get the following error (excerpt from the config.log) .... configure:2708: checking for Kerberos5 installation configure:2712: error: failed to find krb5-config in /usr/kerberos/bin ..... /usr/kerberos/bin is in my PATH. The file krb5-config doesn't exist on the system. From where can I get the missing file? Which versions of the krb5- packages must be installed? Version-Release number of selected component (if applicable): mod_auth_krb5-rc3 How reproducible: every time. Steps to Reproduce: 1. ./configure --with-krb5=/usr/kerberos --with-apache=/opt/apache2 -- without-krb4 2. 3. Actual results: Expected results: Additional info: see the complete config.log
Created attachment 96804 [details] config.log
The krb5-config script wasn't part of MIT Kerberos until version 1.2.3, it would have to be added to 1.2.2. Marking as an enhancement.
Ok. The krb5-devel version 1.2.4-11 includes the krb5-config script. Is this version officially supported by RedHat AS 2.1.?
Created internal RFE bug #113124.
Between 1.2.2 and 1.2.3, the version of the libkadm5clnt shared library changed from 4 to 5, so attempting an update to 1.2.4 might create dependency problems. Barring that, I expect it would work without problems. Whether or not that's supported, I couldn't guess.
Rereading your question, I think you're suggesting extracting just the script from version 1.2.4 of the package and using that. Except for the "version_string" variable (which may or may not be significant, depending on what's calling the script), it should do just fine.
This bug is filed against RHEL2.1, 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.