* k5-int.h (struct krb5_cksumtypes): Add new field trunc_size

ticket: 1621
status: open

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@15647 dc483132-0cff-0310-8789-dd5450dbe970

diff --git a/src/include/ChangeLog b/src/include/ChangeLog
index 71366e826b6221ac43f0cec582347ee128743fb0..a0feb8fcda58fd658aec30ebb1e25cc925d7603f 100644 (file)
--- a/src/include/ChangeLog
+++ b/src/include/ChangeLog
@@ -1,3 +1,7 @@
+2003-06-23  Ken Raeburn  <raeburn@mit.edu>
+
+       * k5-int.h (struct krb5_cksumtypes): Add new field trunc_size.
+
 2003-06-12  Tom Yu  <tlyu@mit.edu>
 
        * krb5.hin: krb524_init_ets() takes one argument.

diff --git a/src/include/k5-int.h b/src/include/k5-int.h
index ee3e65b070bcebe5b9fbb975ce7c198dc5b6136e..fa5b93d69ba076590e5e434697bd65d1ffad9fcd 100644 (file)
--- a/src/include/k5-int.h
+++ b/src/include/k5-int.h
@@ -660,6 +660,12 @@ struct krb5_cksumtypes {
        kind of messy, but so is the krb5 api. */
     const struct krb5_keyhash_provider *keyhash;
     const struct krb5_hash_provider *hash;
+    /* This just gets uglier and uglier.  In the key derivation case,
+       we produce an hmac.  To make the hmac code work, we can't hack
+       the output size indicated by the hash provider, but we may want
+       a truncated hmac.  If we want truncation, this is the number of
+       bytes we truncate to; it should be 0 otherwise.  */
+    unsigned int trunc_size;
 };
 
 #define KRB5_CKSUMFLAG_DERIVE          0x0001