From 241ec6e5c75b6872a32c5e05c17ebb4238e120e0 Mon Sep 17 00:00:00 2001 From: David Benjamin Date: Mon, 19 Aug 2013 05:49:56 -0400 Subject: Bump find_or_insert_uid's time limit Basing it on krb4's CLOCK_SKEW value doesn't make any sense. We pick 900 because it is just over 128 + 256 + 512, the longest group of three timeouts in the retransmit schedule used by the zephyrd. This allows us to miss two packets in a row and still be fine. --- h/internal.h | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'h/internal.h') diff --git a/h/internal.h b/h/internal.h index 0753e67..93d76ab 100644 --- a/h/internal.h +++ b/h/internal.h @@ -19,10 +19,6 @@ #include #endif -#ifndef HAVE_KRB4 -#define CLOCK_SKEW 300 /* max time to cache packet ids */ -#endif - #include #ifdef HAVE_ARPA_NAMESER_COMPAT_H #include @@ -43,6 +39,7 @@ #define Z_FRAGFUDGE 13 /* Room to for multinotice field */ #define Z_NOTICETIMELIMIT 30 /* Time to wait for fragments */ #define Z_INITFILTERSIZE 30 /* Starting size of uid filter */ +#define Z_FILTERTIMELIMIT 900 /* Max time to cache packet ids */ #define Z_AUTHMODE_NONE 0 /* no authentication */ #define Z_AUTHMODE_KRB4 1 /* authenticate using Kerberos V4 */ -- cgit v1.2.3