[2681] in Kerberos-V5-bugs
krb5-build/385: configuration of the crypto libs
daemon@ATHENA.MIT.EDU (root@massena.gr.osf.org)
Wed Mar 5 03:23:48 1997
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: tlyu@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, root@massena.gr.osf.org
Date: Wed, 5 Mar 1997 09:20:17 GMT
From: root@massena.gr.osf.org
Reply-To: root@massena.gr.osf.org
To: krb5-bugs@MIT.EDU
Cc: yp@opengroup.org
>Number: 385
>Category: krb5-build
>Synopsis: in lib/crypto, badly written configure (incoherent mixed disable/without)
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: tlyu
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Wed Mar 05 03:20:01 EST 1997
>Last-Modified:
>Originator: yp@opengroup.org
>Organization:
The Open Group
>Release: 1.0
>Environment:
System: all (script files)
>Description:
In lib/crypto, doing a configure --disable-des-... results
in nothing being done. The reason for this happens to be that it's
describe as a "enable/disable" feature, but works internally
as a "with/without" feature. Another badly written configure item
is that the configure section to do a without works with a "withval"
while the default value ends up being a "enableval". The latter is
the one used in the test to actually enable/disable a given package.
This bug in the configure script is not very critical by itself
(since I've been able to work around it :-), however, disabling
the crypto libs do not work for the utils (kdb5_util, ...) or the
kdc. It is very welcome to be able to specify a Null master-key-type
and Null .*enctype.
>How-To-Repeat:
in lib/crypto:
e.g. ./configure --without-des-cbc-raw --without-rsa-md4
>Fix:
Fix the configure script (help part/test part).
>Audit-Trail:
>Unformatted:
