lp://staging/heimdal

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

1 recipe using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

29685. By Nicolas Williams <email address hidden> on 2022-03-24

kadmin: Fix leak of dup context

29684. By Nicolas Williams <email address hidden> on 2022-03-24

kadm5: Fix leak in kadm5_c_dup_context()

29683. By Nicolas Williams <email address hidden> on 2022-03-24

kadm5: Fix failure to connect in dup handle

29682. By Nicolas Williams <email address hidden> on 2022-03-23

kadmin: Fix re-entrance in iterations

Any callback of kadm5_iter_principals() that wants to call other kadm5
functions (such as kadm5_get_principal()) needs to do so on a different
kadm5 handle than the one used for kadm5_iter_principals().

29681. By Nicolas Williams <email address hidden> on 2022-03-23

doc: Revert part of 0878a568f9e for Texinfo 5.1

0878a568f9e fixed a warning from Texinfo 6.7:

    doc/whatis.texi:33: warning: redefining Texinfo language command: @sub

but the fix makes the doc build fail w/ Texinfo 5.1.

There may still be other problems when using Texinfo 5.1.

29680. By Nicolas Williams <email address hidden> on 2022-03-23

hdb: Tolerate duplicate aliases

One user had an entry with duplicate aliases. This happened with an
earlier version of Heimdal.

This commit does not remove the duplicates, but it does tolerate them.

29679. By Nicolas Williams <email address hidden> on 2022-03-23

kdc: More testing of hard aliases

This is an attempt to make sure we test realm migration aliases by doing
kinit w/ a hard alias name in a different realm, and that we can get
service tickets for services in the same and other realms some of which
are hard aliases in one direction, and some in the other.

29678. By Nicolas Williams <email address hidden> on 2022-03-23

krb5: Fix KCM for root user

29677. By Nicolas Williams <email address hidden> on 2022-03-22

kadmin: LIST interrupt message needs no reply

The online LIST interrupt message is a NOP, but it's expected to not
have a reply (the server doesn't send one if it receives it before the
LIST finishes).

However, if the interrupt message arrives after the LIST finished, then
it does get a reply, and this causes the client to get out of step with
the server.

Fixes include:

1) flavor the interrupt NOP to make sure it never gets a reply,
2) introduce a new kadm_list_interrtupt message that is like a NOP that
   produces no reply
3) always consume -after the LIST ends- a reply to any list interrupt
   NOP on the client side.

This implements (1).

29676. By Nicolas Williams <email address hidden> on 2022-03-22

kadm5: Add missing kadm5_ret_principal_ent() check