From 25cb7ee59277655060fe02fb19a4653ee56703a5 Mon Sep 17 00:00:00 2001 From: Ken Raeburn Date: Tue, 24 Jun 2003 02:10:55 +0000 Subject: [PATCH] * 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 --- src/include/ChangeLog | 4 ++++ src/include/k5-int.h | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/src/include/ChangeLog b/src/include/ChangeLog index 71366e826..a0feb8fcd 100644 --- a/src/include/ChangeLog +++ b/src/include/ChangeLog @@ -1,3 +1,7 @@ +2003-06-23 Ken Raeburn + + * k5-int.h (struct krb5_cksumtypes): Add new field trunc_size. + 2003-06-12 Tom Yu * krb5.hin: krb524_init_ets() takes one argument. diff --git a/src/include/k5-int.h b/src/include/k5-int.h index ee3e65b07..fa5b93d69 100644 --- 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 -- 2.26.2