krb5-1.9.5 is released

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

krb5-1.9.5 is released

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

The MIT Kerberos Team announces the availability of MIT Kerberos 5
Release 1.9.5.  This is the last planned release for the krb5-1.9
series, which has reached the end of its maintenance period.  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.9.5
===================================

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

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

The homepage for the krb5-1.9.5 release is:

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

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:

        http://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 krb5-1.9.5 (2013-04-25)
========================================

This is a bugfix release.  The krb5-1.9 release series has reached the
end of its maintenance period, and krb5-1.9.5 is the last planned
release in the series.  For new deployments, installers should prefer
the krb5-1.11 release series or later.

* Fix KDC null pointer dereference in TGS-REQ handling [CVE-2013-1416]

* Fix PKINIT null pointer dereference vulnerability [CVE-2013-1415]

* Fix KDC heap corruption vulnerability [CVE-2012-1015]

* Prevent the KDC from returning a host-based service principal
  referral to the local realm.

* Incremental propagation could erroneously act as if a slave's
  database were current after the slave received a full dump that
  failed to load.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (SunOS)

iQEVAwUBUXrl8xUCTNN0nXiJAQJYEgf/f/wkN5iAI7xaTDHWRFYLEAhoDaWLVVlC
irCPQKA4I6g7dO9/8bKkQtyCu5ktW99ZI8UvSiWm7CklBjSHQwPk8qn3wF/obbbV
/WemLEJdmIA7CjLCzUeAuomkRSEJo0L3BY8Wbkexiub+ZEAa8UCXY2EfSRPTCVk7
tx6YVtUhSTd87RVTwLwQnMq02difupUsS5ecP7doxxz36W7A8DFdq2IYDUxHAVgz
uf2XoVOeh/7T6Y2Ax/9T1rqkivLqQb8YVRdKz8JGDMqDgoglNkzvS0lLcFbn8qIH
yL4Y3D4/KRBRenfX0BY7T9YQ51WxtEcIMvxOKFDEHWFgdSUcxqkYfw==
=3Yct
-----END PGP SIGNATURE-----

_______________________________________________
kerberos-announce mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/kerberos-announce