#1385 heimdal: compile time diference
Closed: Invalid None Opened 10 years ago by rambaldi.


I tried to compile sssd 1.8.4 with heimdal as kerberos provider but encountered some compile time errors. sssd 1.8.3 compiles (and runs) just fine.

The compile errors are all in src/util/sss_krb5.c and all related to a different name in the structure krb5_keytab_entry used by heimdal.

Ie this line fails:
if (!krb5_c_valid_enctype(entry.key.enctype) ||

when in change it to
if (!krb5_c_valid_enctype(entry.keyblock.keytype) ||

it fixes this occurrence. The entry.key.enctype is used 4 times in this file and when I change all of them in one go by this sed expression:

sed -i 's/entry.key.enctype/entry.keyblock.keytype/g' src/util/sss_krb5.c

sssd 1.8.4 compiles (and runs) again.

I know, a real solution should work on both MIT and Heimdal. But this illustrates both the problem and the solution (I hope)


SSSD relies on multiple features that are not available in Heimdal, and SSSD 1.9.0 will rely on many more still (such as DIR: cache support). We do not support compiling against Heimdal.

Patches will be accepted to improve Heimdal support, but the core upstream development team will not invest any time in maintaining it.

resolution: => wontfix
status: new => closed

This patch restores compiling against Heimdal.

Please consider it for submission.

patch: 0 => 1
resolution: wontfix =>
status: closed => reopened

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0 beta 4
priority: major => minor
rhbz: => 0
type: defect => task

This issue, and patch are now obsolete due to the revert patch: 0001-Revert-commit-4c157ec.patch

Fields changed

resolution: => invalid
status: reopened => closed

Metadata Update from @rambaldi:
- Issue set to the milestone: SSSD 1.9.0 beta 4

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2427

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.