krb5-1.16 is released

[Greg Hudson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The MIT Kerberos Team announces the availability of MIT Kerberos 5
Release 1.16.  Please see below for a list of some major changes
included, or consult the README file in the source tree for a more
detailed list of significant changes.

RETRIEVING KERBEROS 5 RELEASE 1.16
==================================

You may retrieve the Kerberos 5 Release 1.16 source from the
following URL:

        https://kerberos.org/dist/

(The distribution URL has changed from previous releases.  The same
contents are available at the old URL.)

The homepage for the krb5-1.16 release is:

        http://web.mit.edu/kerberos/krb5-1.16/

Further information about Kerberos 5 may be found at the following
URL:

        http://web.mit.edu/kerberos/

and at the MIT Kerberos Consortium web site:

        https://www.kerberos.org/

DES transition
==============

The Data Encryption Standard (DES) is widely recognized as weak.  The
krb5-1.7 release contains measures to encourage sites to migrate away
- - From using single-DES cryptosystems.  Among these is a configuration
variable that enables "weak" enctypes, which defaults to "false"
beginning with krb5-1.8.


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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBWicDFAy6CFdfg3LfAQKMJQ//Vwxra3pYahgggcfOKM0kj2YMc/hlfzm1
bpqBi/X7BKHg2XcZx7iB5wpNg57Y8iUVm09RSyhoCrbL1wud9SFDJXSz3B+TVMQR
Uzx0RuZgAsG++dKLdmYHjfHKt3sr9UXOuf+qXXPHMSeO5vxH2Kb9qU9dY2vs4oHY
xlYBRTlp5ww51i62d9SfowtRGceHIERa95O3G8tgXohrlKfSUZqsHQBYiwAP98m0
M7PA7XiIpj0mhaIOlH+Fhxv2rZwtZlNMWVwNwmE7Zq2F0FXpKLBuAOkrmtHPrQ8v
uiOiVR46hACZwG9BOU9SqSbfAEJszrEtGgLqU3Zi6l+sSkXUPWZUCL3Vrv33fxdk
KxYiZ8/OxKXES+VWlpib1pZdTglnc72Kh7KCsdlVtGKI8WkSnJnAu/KQJQw0f/Ou
IiOsB22WEYS5BMd9sJvJXdtuJUbpxgTH38XyqvRh8zN7jkd2bWst9J4UTzod6rlb
bIe5WmvD6/4UHUApnGsipjBRPzOHA7zn4WIdxNf2WwL7SdWI9Bds524SfEvYN1uw
iHGNLHHGjU45rSbGGGHpOksnAjf8Aswie9s1NESAwIKMYpsoxrnqr82gJG9uuHm9
Y6i5S+IoKbD/fwszpIXMBlMxFBwesiNwQWrP4rNZS+BJZ6PHCeXb6DIGpkUOEfX7
JLQAxKITE4M=
=pEAI
-----END PGP SIGNATURE-----