2010-03-05 22:19:38 +00:00
|
|
|
Fall back to TCP on kdc-unresolvable/unreachable errors. We still have
|
|
|
|
to wait for UDP to fail, so this might not be ideal. RT #5868.
|
|
|
|
|
2011-11-09 23:44:01 +00:00
|
|
|
--- krb5/src/lib/krb5/os/changepw.c
|
|
|
|
+++ krb5/src/lib/krb5/os/changepw.c
|
|
|
|
@@ -270,10 +270,22 @@ change_set_password(krb5_context context
|
|
|
|
&callback_info, &chpw_rep, ss2sa(&remote_addr),
|
|
|
|
&addrlen, NULL, NULL, NULL);
|
|
|
|
if (code) {
|
2010-03-05 22:19:38 +00:00
|
|
|
- /*
|
|
|
|
- * Here we may want to switch to TCP on some errors.
|
|
|
|
- * right?
|
|
|
|
- */
|
|
|
|
+ /* if we're not using a stream socket, and it's an error which
|
|
|
|
+ * might reasonably be specific to a datagram "connection", try
|
|
|
|
+ * again with a stream socket */
|
2011-11-09 23:44:01 +00:00
|
|
|
+ if (!use_tcp) {
|
2010-03-05 22:19:38 +00:00
|
|
|
+ switch (code) {
|
|
|
|
+ case KRB5_KDC_UNREACH:
|
|
|
|
+ case KRB5_REALM_CANT_RESOLVE:
|
|
|
|
+ case KRB5KRB_ERR_RESPONSE_TOO_BIG:
|
|
|
|
+ /* should we do this for more result codes than these? */
|
2011-11-09 23:44:01 +00:00
|
|
|
+ k5_free_serverlist (&sl);
|
|
|
|
+ use_tcp = 1;
|
2010-03-05 22:19:38 +00:00
|
|
|
+ continue;
|
|
|
|
+ default:
|
|
|
|
+ break;
|
|
|
|
+ }
|
|
|
|
+ }
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|