Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by krbdev.mit.edu (8.9.3) with ESMTP id NAA29834; Wed, 26 Mar 2003 13:32:39 -0500 (EST) Received: from 216-239-45-4.google.com (216-239-45-4.google.com [216.239.45.4]) by pacific-carrier-annex.mit.edu (8.12.4/8.9.2) with ESMTP id h2QIWceM015136 for ; Wed, 26 Mar 2003 13:32:38 -0500 (EST) Received: from moma.corp.google.com (moma.corp.google.com [10.3.0.12]) by 216-239-45-4.google.com (8.12.6/8.12.3) with ESMTP id h2QIWb3u020960 for ; Wed, 26 Mar 2003 10:32:37 -0800 Received: from moma.corp.google.com (localhost [127.0.0.1]) by moma.corp.google.com (8.12.8/8.12.3) with ESMTP id h2QIWbwC008723 for ; Wed, 26 Mar 2003 10:32:37 -0800 Received: (from frank@localhost) by moma.corp.google.com (8.12.8/8.12.3) id h2QIWbF0008720 for krb5-bugs@mit.edu; Wed, 26 Mar 2003 10:32:37 -0800 Date: Wed, 26 Mar 2003 10:32:37 -0800 From: Frank Cusack To: krb5-bugs@mit.edu Subject: MAX_SKDC_TIMEOUT misleading Message-Id: <20030326103237.B7241@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-RT-Original-Encoding: us-ascii Content-Length: 363 This value is set to 30 by default, however the code which uses it (sendto_kdc.c) does an exponential backoff: for (timeout = krb5_skdc_timeout_1; timeout < krb5_max_skdc_timeout; timeout <<= krb5_skdc_timeout_shift) { The actual max value used is 16s. Setting it to 30 is misleading. I'd say change this to 16, but an alternative is 32. thx /fc