Jan Harkes <jaharkes_at_cs.cmu.edu> writes:

> I thought I did try heimdal when I was writing the configure tests.
> Did you try './configure --with-crypto', without that flag the code
> never even tries to look for installed crypto related libraries.

Yup.  It chokes during compilation, when the code in krb5.c grovels
down into data structures that don't look the same in Heimdal and MIT
Kerberos.  This bit, for instance:

    /* Check whether the realm is correct */
    if (strncmp(ticket->enc_part2->client->realm.data, kerberos5realm,
		ticket->enc_part2->client->realm.length)) {
	/* names differ */
	fprintf(stderr, "incorrect realm in ticket\n");
	goto out;    
    }

The krb5_ticket structure has no enc_part2, and I notice that the
existing API includes access functions that get the realm string (and
its length) out of the ticket.  IIRC, there were not very many such
errors compiling the code, so it's probably not that much work fixing
it -- but I thought I'd see if anyone else had done it, first.  :-)

-tih
-- 
Tom Ivar Helbekkmo, Senior System Administrator, EUnet Norway
www.eunet.no  T: +47-22092958 M: +47-93013940 F: +47-22092901