mit-krb5 and heimdal binaries

ronnie sahlberg ronniesahlberg at
Sun Mar 19 07:49:16 UTC 2023

Kerberos is important.

I think the question is which kerberos implementation has best
support, has best tooling, has best and prompt responses to CVEs or
and which one is going to be the most common uses by the target audience/users.
I.e. which one is most mature and will cause the least maintenance
overhead to the samba devs?

On Sun, 19 Mar 2023 at 16:13, Michael Tokarev via samba-technical
<samba-technical at> wrote:
> Hi!
> I already asked a similar question before, but it keeps popping up in different
> contexts and forms, and the more I use samba myself, the more often it comes to
> me too, especially in context of using various security tokens for auth.  And the
> more I think about all this, the more sane it looks to me.
> The thing is: mit-krb5 has much better user-level support than heimdal. But samba
> does not fully support mit-krb5 as an active directory domain controller.  The
> AD-DC thing is server-side.
> I can think of providing two builds of samba for a distribution (eg debian/ubuntu), -
> one implementing whole ad-dc, as a complete thing, using their own set of libs,
> linked with heimdal. And a usual set of more client-side packages, with their own
> libraries, built against mit-krb5.  Or maybe some other combination also has its
> right to be, - for example, smbclient built with mit-krb5, the rest is heimdal.
> An essential part of this is that the two sets (built against mit-krb5 and heimdal)
> do not share any internal libraries, each has its own libraries. This way, there's
> no "mix" of differently built samba, each build uses only its own libs, so there's
> no clash here.  They share the same smb.conf though.
> So far, I've seen requests to build two versions of the server (again, with mit-krb5
> and with heimdal), - and I faced the same issues too.  This is because a regular AD
> member server is also good to have mit-krb5 support to integrate nicely into the auth
> infrastructure. While for ad-dc, it is less often used as "end-user" server.
> So I can think of a separate samba-ad-dc binary package providing whole samba suite
> built against heimdal (maybe without smbclient and some other minor things), and
> samba "file server" binary package providing regular server not suitable to use as
> an ad-dc, but conflicting with samba-ad-dc, so it is not possible to install one
> together with another.
> This approach also has another good side effect, to discourage usage of samba-ad-dc
> as a regular file server.
> Or maybe the whole thing is moot now, and we just can provide regular samba built
> against mit-krb5 to work as a good AD-DC?  That would be the best solution IMHO.
> Thanks,
> /mjt

More information about the samba-technical mailing list