krb5: Expand list of vector types that are hashed
So that we can eventually use iovec hashes with encrypt, as well as sign operations, add CRYPTO_TYPE_HEADER and CRYPTO_TYPE_PADDING to the list of iovecs which will be hashed.
This commit is contained in:

committed by
Jeffrey Altman

parent
2d84fc65bb
commit
550067f6d0
@@ -1425,7 +1425,10 @@ iov_sign_data_len(krb5_crypto_iov *data, int num_data)
|
||||
size_t i, len;
|
||||
|
||||
for (len = 0, i = 0; i < num_data; i++) {
|
||||
if (_krb5_crypto_iov_should_sign(&data[i]))
|
||||
/* Can't use should_sign, because we must only count data, not
|
||||
* header/trailer */
|
||||
if (data[i].flags == KRB5_CRYPTO_TYPE_DATA ||
|
||||
data[i].flags == KRB5_CRYPTO_TYPE_SIGN_ONLY)
|
||||
len += data[i].data.length;
|
||||
}
|
||||
|
||||
|
@@ -186,7 +186,9 @@ static inline int
|
||||
_krb5_crypto_iov_should_sign(const struct krb5_crypto_iov *iov)
|
||||
{
|
||||
return (iov->flags == KRB5_CRYPTO_TYPE_DATA
|
||||
|| iov->flags == KRB5_CRYPTO_TYPE_SIGN_ONLY);
|
||||
|| iov->flags == KRB5_CRYPTO_TYPE_SIGN_ONLY
|
||||
|| iov->flags == KRB5_CRYPTO_TYPE_HEADER
|
||||
|| iov->flags == KRB5_CRYPTO_TYPE_PADDING);
|
||||
}
|
||||
|
||||
/* NO_HCRYPTO_POLLUTION is defined in pkinit-ec.c. See commentary there. */
|
||||
|
Reference in New Issue
Block a user