bluejekyll / trust-dns / 877

82%

Pull #198

travis-ci

Clarify what values are digests and what values are to-be-digested/signed.

During a previous refactoring the digesting of message contents was moved closer
to the place where the signing is done, to accomodate Ed25519 and crypto APIs
that don't take digests as input to signining functions. However, functions that
used to return digests kept their names with a "_hash" suffix or "hash_" prefix,
which is confusing.

Clarify that by renaming all such functions. Further, introduce a new TBS wrapper
type that further clarifies the intent of the code. "TBS" is a common shorthand
in crypto code standing for "to be signed" data, e.g. tbsCertificate in X.509.

75 of 75 new or added lines in 4 files covered. (100.0%)

9406 of 10686 relevant lines covered (88.02%)

0.88 hits per line