Skip Menu |
 

From: ghudson@mit.edu
Subject: SVN Commit

In PAC signatures, the hmac-md5 checksum type can be used with AES
keys. Make this work by removing the enc field from the hmac-md5 and
md5-hmac checksum types, and adding a check in
krb5int_hmacmd5_checksum() for a null key or a key which is longer
than the hash block size (64 bytes for MD5). The checksum algorithm
only uses the key bits; it does invoke the cipher.

The checksum type names are kind of wrong, but we'll leave them alone
for compatibility. The descriptions are updated.


https://github.com/krb5/krb5/commit/3460c7dd68147d2a343893752ad9cd29d74f5def
Commit By: ghudson
Revision: 24191
Changed Files:
U trunk/src/lib/crypto/krb/checksum/hmac_md5.c
U trunk/src/lib/crypto/krb/cksumtypes.c
This was reported by Douglas E. Engert <deengert@anl.gov>. Pointers to
the krbdev discussion thread:

http://mailman.mit.edu/pipermail/krbdev/2010-June/009145.html
http://mailman.mit.edu/pipermail/krbdev/2010-July/009147.html
From: tlyu@mit.edu
Subject: SVN Commit

pull up r24191 from trunk

------------------------------------------------------------------------
r24191 | ghudson | 2010-07-19 01:01:45 -0400 (Mon, 19 Jul 2010) | 15 lines

ticket: 6751
subject: Allow Microsoft HMAC-MD5 checksum types to use non-RC4 keys
target_version: 1.8.3
tags: pullup

In PAC signatures, the hmac-md5 checksum type can be used with AES
keys. Make this work by removing the enc field from the hmac-md5 and
md5-hmac checksum types, and adding a check in
krb5int_hmacmd5_checksum() for a null key or a key which is longer
than the hash block size (64 bytes for MD5). The checksum algorithm
only uses the key bits; it does invoke the cipher.

The checksum type names are kind of wrong, but we'll leave them alone
for compatibility. The descriptions are updated.

https://github.com/krb5/krb5/commit/f8187320050800d1e68c11913e9ab841edd13576
Commit By: tlyu
Revision: 24198
Changed Files:
U branches/krb5-1-8/src/lib/crypto/krb/checksum/hmac_md5.c
U branches/krb5-1-8/src/lib/crypto/krb/cksumtypes.c