Log Message:
mit-krb5: update to 1.16.1

Major changes in 1.16.1 (2018-05-03)

This is a bug fix release.

    Fix flaws in LDAP DN checking, including a null dereference KDC crash which \ 
could be triggered by kadmin clients with administrative privileges \ 
[CVE-2018-5729, CVE-2018-5730].
    Fix a KDC PKINIT memory leak.
    Fix a small KDC memory leak on transited or authdata errors when processing \ 
TGS requests.
    Fix a regression in pkinit_cert_match matching of client certificates \ 
containing Microsoft UPN SANs.
    Fix a null dereference when the KDC sends a large TGS reply.
    Fix "kdestroy -A" with the KCM credential cache type.
    Allow validation of Microsoft PACs containing enterprise names.
    Fix the handling of capaths "." values.
    Fix handling of repeated subsection specifications in profile files (such as \ 
when multiple included files specify relations in the same subsection).

Major changes in 1.16 (2017-12-05)

Administrator experience:
        The KDC can match PKINIT client certificates against the \ 
"pkinit_cert_match" string attribute on the client principal entry, \ 
using the same syntax as the existing "pkinit_cert_match" profile \ 
option.
        The ktutil addent command supports the "-k 0" option to ignore \ 
the key version, and the "-s" option to use a non-default salt string.
        kpropd supports a --pid-file option to write a pid file at startup, when \ 
it is run in standalone mode.
        The "encrypted_challenge_indicator" realm option can be used \ 
to attach an authentication indicator to tickets obtained using FAST encrypted \ 
challenge pre-authentication.
        Localization support can be disabled at build time with the \ 
--disable-nls configure option.

Developer experience:
        The kdcpolicy pluggable interface allows modules control whether tickets \ 
are issued by the KDC.
        The kadm5_auth pluggable interface allows modules to control whether \ 
kadmind grants access to a kadmin request.
        The certauth pluggable interface allows modules to control which PKINIT \ 
client certificates can authenticate to which client principals.
        KDB modules can use the client and KDC interface IP addresses to \ 
determine whether to allow an AS request.
        GSS applications can query the bit strength of a krb5 GSS context using \ 
the GSS_C_SEC_CONTEXT_SASL_SSF OID with gss_inquire_sec_context_by_oid().
        GSS applications can query the impersonator name of a krb5 GSS \ 
credential using the GSS_KRB5_GET_CRED_IMPERSONATOR OID with \ 
gss_inquire_cred_by_oid().
        kdcpreauth modules can query the KDC for the canonicalized requested \ 
client principal name, or match a principal name against the requested client \ 
principal name with canonicalization.

Protocol evolution:
        The client library will continue to try pre-authentication mechanisms \ 
after most failure conditions.
        The KDC will issue trivially renewable tickets (where the renewable \ 
lifetime is equal to or less than the ticket lifetime) if requested by the \ 
client, to be friendlier to scripts.
        The client library will use a random nonce for TGS requests instead of \ 
the current system time.
        For the RC4 string-to-key or PAC operations, UTF-16 is supported \ 
(previously only UCS-2 was supported).
        When matching PKINIT client certificates, UPN SANs will be matched \ 
correctly as UPNs, with canonicalization.

User experience:
        Dates after the year 2038 are accepted (provided that the platform time \ 
facilities support them), through the year 2106.
        Automatic credential cache selection based on the client realm will take \ 
into account the fallback realm and the service hostname.
        Referral and alternate cross-realm TGTs will not be cached, avoiding \ 
some scenarios where they can be added to the credential cache multiple times.
        A German translation has been added.

Code quality:
        The build is warning-clean under clang with the configured warning options.
        The automated test suite runs cleanly under AddressSanitizer.

Major changes in 1.15.3 (2018-05-03)

This is a bug fix release.

    Fix flaws in LDAP DN checking, including a null dereference KDC crash which \ 
could be triggered by kadmin clients with administrative privileges \ 
[CVE-2018-5729, CVE-2018-5730].
    Fix a KDC PKINIT memory leak.
    Fix a small KDC memory leak on transited or authdata errors when processing \ 
TGS requests.
    Fix a null dereference when the KDC sends a large TGS reply.
    Fix "kdestroy -A" with the KCM credential cache type.
    Fix the handling of capaths "." values.
    Fix handling of repeated subsection specifications in profile files (such as \ 
when multiple included files specify relations in the same subsection).

Major changes in 1.15.2 (2017-09-25)

This is a bug fix release.

    Fix a KDC denial of service vulnerability caused by unset status strings \ 
[CVE-2017-11368]
    Preserve GSS contexts on init/accept failure [CVE-2017-11462]
    Fix kadm5 setkey operation with LDAP KDB module
    Use a ten-second timeout after successful connection for HTTPS KDC requests, \ 
as we do for TCP requests
    Fix client null dereference when KDC offers encrypted challenge without FAST
    Ignore dotfiles when processing profile includedir directive
    Improve documentation

Major changes in 1.15.1 (2017-03-01)

This is a bug fix release.

    Allow KDB modules to determine how the e_data field of principal fields is freed
    Fix udp_preference_limit when the KDC location is configured with SRV records
    Fix KDC and kadmind startup on some IPv4-only systems
    Fix the processing of PKINIT certificate matching rules which have two \ 
components and no explicit relation
    Improve documentation

Major changes in 1.15 (2016-12-01)

Administrator experience:
        Improve support for multihomed Kerberos servers by adding options for \ 
specifying restricted listening addresses for the KDC and kadmind.
        Add support to kadmin for remote extraction of current keys without \ 
changing them (requires a special kadmin permission that is excluded from the \ 
wildcard permission), with the exception of highly protected keys.
        Add a lockdown_keys principal attribute to prevent retrieval of the \ 
principal's keys (old or new) via the kadmin protocol. In newly created \ 
databases, this attribute is set on the krbtgt and kadmin principals.
        Restore recursive dump capability for DB2 back end, so sites can more \ 
easily recover from database corruption resulting from power failure events.
        Add DNS auto-discovery of KDC and kpasswd servers from URI records, in \ 
addition to SRV records. URI records can convey TCP and UDP servers and master \ 
KDC status in a single DNS lookup, and can also point to HTTPS proxy servers.
        Add support for password history to the LDAP back end.
        Add support for principal renaming to the LDAP back end.
        Use the getrandom system call on supported Linux kernels to avoid \ 
blocking problems when getting entropy from the operating system.
        In the PKINIT client, use the correct DigestInfo encoding for PKCS #1 \ 
signatures, so that some especially strict smart cards will work.

Code quality:
        Clean up numerous compilation warnings.
        Remove various infrequently built modules, including some preauth \ 
modules that were not built by default.

Developer experience:
        Add support for building with OpenSSL 1.1.
        Use SHA-256 instead of MD5 for (non-cryptographic) hashing of \ 
authenticators in the replay cache. This helps sites that must build with FIPS \ 
140 conformant libraries that lack MD5.
        Eliminate util/reconf and allow the use of autoreconf alone to \ 
regenerate the configure script.

Protocol evolution:
        Add support for the AES-SHA2 enctypes, which allows sites to conform to \ 
Suite B crypto requirements.