[krbdev.mit.edu #2240] krb5-config --cflags gssapi whenusedbyOpenSSH-snap-20040212

Darren Tucker via RT rt-comment at krbdev.mit.edu
Mon Feb 23 08:43:24 EST 2004


Sam Hartman wrote:
>>>>>>"Douglas" == Douglas E Engert <deengert at anl.gov> writes:
[gssapi.h not in include path supplied by krb5-config --cflags]
>     Douglas> The Heimdal code (as I understand) does
>     Douglas> not have this problem, so does not execute this code.

Heimdal's gssapi.h is /path/to/heimdal/include/gssapi.h

> Hi.  MIT has not made a determination as to whether Doug's bug is
> actually a bug nor whether we will fix it.  We certainly will not fix
> it for the upcoming 1.3.2 release; we have passed our final change
> deadline for that release.

Fair enough WRT the pending release.

> I disagree with Doug's assertion that most programs include gssapi.h
> not gssapi/gssapi.h.

In a highly unscientific Google survey, it's close to even:

Searched the web for "#include <gssapi/gssapi.h>". Results 1 - 10 of
about 555.

Searched the web for "#include <gssapi.h>". Results 1 - 10 of about 503.

Interestingly, one of those is a complaint about this very issue from 1998!

> AT this time I would recommend including gssapi.h for Heimdal and
> gssapi/gssapi.h for MIT Kerberos.

Am I the only one that thinks it's silly that you can't write a single
"#include <[something]gssapi.h>" that works with both MIT and Heimdal's
supplied --cflags?  Yay for standards.

Anyway, I will be adding AC_CHECK_HEADERS tests to configure to check
for <gssapi.h> and <gssapi/gssapi.h>.

> We'll certainly evaluate Doug's bug report and make a determination
> about whet we think the correct behavior is.  However I am very
> reluctant to recommend that people accept patches that depend on the
> specific output of krb5-config.

BTW: I don't like the sed hackery to used to split the output of
krb5-config --libs, and I wrote it.  I did it because OpenSSH's
configure tracks LIBS and LDFLAGS separately, I didn't want to change
its behaviour in this regard.

We might do away with it if we have some confidence that the resulting
link-order changes won't break something, somewhere.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.



More information about the krb5-bugs mailing list