This bug was fixed in the package sssd - 1.8.2-0ubuntu1
---
sssd (1.8.2-0ubuntu1) precise; urgency=low
* Merge from Debian git, remaining changes:
- control, rules: Drop libsemanage-dev from build-depends, it's not
in main and will not be for precise. Configure
Added the heimdal as an option, committed in git. Also lowered the
dependency as Recommends.
** Changed in: sssd (Ubuntu)
Importance: Undecided = Low
** Changed in: sssd (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
That seems reasonable.
Any particular reason you prefer the Heimdal implementation, btw? I've
never really noticed much difference for the PAM modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well I guess your comment regarding similarity between the MIT and
Heimdal GSSAPI module implementations is spot on. They seem to work
identically. But for utils I prefer heimdal-clients over krb5-user. Of
course there's nothing preventing one from using the MIT GSSAPI module
and Heimdal clients,
Note from upstream: Heimdal support is spotty at best. We have some
contributed patches that enable support for most features of Heimdal,
but they are untested by upstream.
We strongly recommend using MIT kerberos with SSSD at this time. If you
choose to switch to Heimdal, you will be required to
On Tue, Mar 27, 2012 at 12:57:38PM -, Stephen Gallagher wrote:
Note from upstream: Heimdal support is spotty at best. We have some
contributed patches that enable support for most features of Heimdal,
but they are untested by upstream.
We strongly recommend using MIT kerberos with SSSD
Sorry, my previous comment was unclear.
There is no formal support for Heimdal in the upstream SSSD. We have
accepted some submissions in the past that make it possible for the SSSD
services to operate with the Heimdal client libraries, but they are
known to function in a degraded mode (some
Yes this change would not change the way sssd is built on Ubuntu or
against which Kerberos implementation the binaries/libraries are linked
against. It would just allow usage of the Heimdal GSSAPI module which is
load at runtime if GSSAPI is enabled. With the way the dependecies are
currently
