summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorKen Raeburn <raeburn@mit.edu>2003-06-20 01:28:49 +0000
committerKen Raeburn <raeburn@mit.edu>2003-06-20 01:28:49 +0000
commit35f071931d91ae3d4e230fbf01441c6aeee617f9 (patch)
tree8f9712454d830bbe47166e87202bda4943f957e5 /README
parent56c9be53e44b322897509a0ee0706ff8b4799bcf (diff)
downloadkrb5-35f071931d91ae3d4e230fbf01441c6aeee617f9.tar.gz
krb5-35f071931d91ae3d4e230fbf01441c6aeee617f9.tar.xz
krb5-35f071931d91ae3d4e230fbf01441c6aeee617f9.zip
Put in some IPv6 details.
Mention db4 compatibility is untested. ticket: 1600 status: open tags: pullup git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@15636 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'README')
-rw-r--r--README12
1 files changed, 10 insertions, 2 deletions
diff --git a/README b/README
index 9bedcf67bc..68e56477f2 100644
--- a/README
+++ b/README
@@ -72,8 +72,13 @@ Notes, Major Changes, and Known Bugs for 1.3
that will probably frustrate any attempts to run this code under SunOS
4 or other pre-C89 systems.
-* Some new code, bug fixes, and cleanup for IPv6 support. [[TODO:
- Insert list of (non-)supporting programs and libraries here.]]
+* Some new code, bug fixes, and cleanup for IPv6 support. Most of the
+ code should support IPv6 transparently now. The RPC code (and
+ therefore the admin system, which is based on it) does not yet
+ support IPv6. The support for Kerberos 4 may work with IPv6 in very
+ limited ways, if the address checking is turned off. The FTP client
+ and server do not have support for the new protocol messages needed
+ for IPv6 support (RFC 2429).
* We have upgraded to autoconf 2.52 (or later), and the syntax for
specifying certain configuration options have changed. For example,
@@ -95,6 +100,9 @@ Notes, Major Changes, and Known Bugs for 1.3
can be used to help the compiler and linker find the installed
packages; see the build documentation for details.
+ We have not tested this change with version 4 of the Berkeley DB
+ library.
+
* The AES cryptosystem has been implemented. However, support in the
Kerberos GSSAPI mechanism has not been written (or even fully
specified), so it's not fully enabled. See the documentation for