structure holds a Kerberos checksum.
There is no component inside
that is directly referable.
The functions are used to create and verify checksums.
creates a checksum of the specified data, and puts it in
specifies the checksum type to use; it must not be keyed. Otherwise
is an encryption context created by
specifies a key-usage.
against the provided data.
returns true is the specified checksum is collision proof (that its
very unlikely that two strings has the same hash value, and that its
hard to find two strings that has the same hash). Examples of
collision proof checksums are MD5, and SHA1, while CRC32 is not.
returns true if the specified checksum type is keyed (that the hash
value is a function of both the data, and a separate key). Examples of
keyed hash algorithms are HMAC-SHA1-DES3, and RSA-MD5-DES. The
hash functions MD5, and SHA1 are not keyed.
returns the checksum type that will be used when creating a checksum for the given
This function is useful in combination with
when you want to know the size a checksum will
use when you create it.
returns 0 or an error if the checksumtype is implemented and not
currently disabled in this kerberos library.
returns the size of the outdata of checksum function.
returns a copy of the checksum
should use used to free the
free the checksum and the content of the checksum.
frees the content of checksum in
calculates the HMAC over
using the keyusage
Note that keyusage is not always used in checksums.
globally disables the checksum type.