These tar files contain three gzipped tar files (src, crypto, and doc) and their associated PGP signature files.
Here are the diffs between 1.0.5 and 1.0.6 ( %R/krb5/krb5-1.0.5-1.0.6.diff.tar">tar file, 74k ).
Here are the diffs between 1.0.4 and 1.0.5 ( %R/krb5/krb5-1.0.4-1.0.5.diff.tar">tar file, 48k ).
Here are the diffs between 1.0.3 and 1.0.4 ( %R/krb5/krb5-1.0.3-1.0.4.diff.tar">tar file, 15k ).
Here are the diffs between patchlevel 2 and patchlevel 3( %R/krb5/krb5-1.0.2-1.0.3.diff.tar">tar file, 15k ).
Here are the diffs between patchlevel 1 and patchlevel 2 ( %R/krb5/krb5-1.0.1-1.0.2.diff.tar">tar file, 13k ).
Here are the diffs between patchlevel 0 and patchlevel 1 ( %R/krb5/krb5-1.0pl1.diffs.tar">tar file, 71k ).
Binary distributions are not available for krb5-1.0.6. The following are only for patchlevel 1 and patchlevel 0.
Binary distributions of Kerberos V5 are provided merely as convenience to those people who wish to try out Kerberos V5 without needing to do a full compile of Kerberos.
MIT and the MIT Kerberos V5 development team make no guarantees that we will continue to supply binary distributions for future releases of Kerberos V5, or for any operating system/platform in particular. These binary distributions have been prepared by members of the MIT Kerberos V5 development team, or by volunteers who have graciously agreed to test the pre-release snapshot. Each binary build is PGP signed by the person who prepared the binary distribution for that particular platform.
While the binary distribution is supposed to correspond exactly to the 1.0 Patchlevel 1 Kerberos V5 source release, you have no way of knowing whether the person who prepared the binary release might have inserted a trojan horse, or a trapdoor. For all you know, the binary distribution might be mailing all of your Kerberos keys to kremvax!boris. (The same is true for the source distribution, but at least you can audit the code yourself!)
For this reason, if you are planning on using Kerberos V5 in production, we strongly suggest that you obtain the source distribution and compile it from source yourself.
Each tar file contains a gzipped tar file containing the binary distribution and its associated PGP signature file.
In order to verify the PGP signatures on the binary distributions, you will also need the PGP keys of the builders.
The following ALPHA snapshot is intended for developers only. It is a snapshot of our main development branch, and contains updated NT support code. Unlike the the ALPHA1 snapshot, the GSSAPI library and the GSS test application now work. The Krb5 DLL has now been separated into multiple DLL files, for better ease of maintenance.
The following known problems still remain:
In addition, we are continueing to work on this release on an on-going basis, so if you plan to be doing any NT work, you should contact us at krbdev@mit.edu, so that we can more properly coordinate our work. NT support has been folded in to the mainline release and will definitely be part of the next major release.
This NT ALPHA 2 snapshot may also be used by developers only to evaluate our new Unix shared library build architecture. It has been significantly revamped since the 1.0 release, to make it easier to support new architectures. The snapshot should have shared library support for the following architectures: AIX 3.x, Linux, NetBSD/i386, NetBSD/pmax, OSF/1, Solaris 2.4. Patches for other architectures are welcome.
This release is not recommended for production. We will be shortly (by mid-April) releasing a 1.0 patchlevel 1 release to fix the most critical bugs found in the Kerberos V5 1.0 release. (The 1.1 release should be out in Summer '97.) Production sites are advised to wait for patchlevel 1.
This Alpha snapshot is available as in the following forms:
n.b. The Windows NT sources are the result of unpacking the Unix sources and running the command "make -f Makefile.in kerbsrc-nt.zip"
Kerberos for Macintosh 2.0.2 includes: KClient 1.8 for Kerberos V4 functionality, and the various pieces that make up Kerberos V5 for Macintosh 2.0.2 (using a stable snapshot of the 1.1 beta Kerberos V5 source from May, 1999).
There are currently three levels of packages: binaries only, SDKs, and source. The binary distribution is for sites who need to localize and redistribute for their end users. The SDKs are for application and library programmers to add Kerberos functionality to their code but don't want to rebuild everything from scratch. The source is for people who need to debug Kerberos or want to build the libraries from scratch.
Requirements
All archives require Stuffit Expander 5.0 or later to expand them.
Client binaries only
Note: While the secure version of Fetch is being distributed from MIT, support for this version is still provided by the original developers at Dartmouth. All questions and bugs should be sent to: fetch@dartmouth.edu
Fetch 3.0.4 beta 6 Secure ( %R/krb5/Fetch_3.0.4b6sec.sit.hqx"> Stuffit 5 and Binhex file, 768K, 5/27/1999)
CNS is the Cygnus Network Security release of Kerberos version 4. It is based on years of continued development starting from earlier MIT V4 releases. The last release available from Cygnus was 96q1; 96q4 has one minor security fix over 96q1. A further release with a number of portability enhancements is planned.
CNS is a available as a %R/krb5/cns-96q4.tar.gz">compressed tar file (approximately 1600k).
Have a nice day!