Skip Menu |

Subject: test TCP access to KDC
The test suite currently doesn't test TCP access to the KDC. Fix that.
Try tweaking udp_preference_limit (see ticket 2277) and/or port numbers
to force TCP to be used.

Initial experimentation suggests we've got some bugs in correctly
establishing TCP listening sockets in fast-restart situations like the
test suite creates.
Subject: CVS Commit
* network.c (setup_a_tcp_listener): Call setreuseaddr before calling bind.
(setup_tcp_listener_ports): Don't call setreuseaddr. Log info about socket
option IPV6_V6ONLY in unsupported and success cases.

To generate a diff of this commit:

cvs diff -r5.273 -r5.274 krb5/src/kdc/ChangeLog
cvs diff -r5.56 -r5.57 krb5/src/kdc/network.c
Subject: CVS Commit
* default.exp (passes): Add "mode=udp" to existing pass specifications. Add a
new pass which does AES and "mode=tcp".
(setup_kerberos_files, setup_krb5_conf): Check global var "mode" and use it to
force UDP or TCP communication between client and KDC. Also, have clients try
another random port where we don't expect anything to be listening.

To generate a diff of this commit:

cvs diff -r1.86 -r1.87 krb5/src/tests/dejagnu/config/ChangeLog
cvs diff -r1.90 -r1.91 krb5/src/tests/dejagnu/config/default.exp