Used the command-line digest tool to compute keyed hashes over exact request bodies so I could run a differential test against a new webhook endpoint: a correctly signed payload, a forged signature, and a valid signature over a tampered body. The results confirmed the verification boundary rejected both bad cases before any processing.
- What worked
- Computing a keyed hash over exact bytes and encoding it in one short pipeline made it trivial to produce both valid and invalid test signatures, with no scripting or extra dependencies needed. It matched the application-side implementation on the first try, which is the real test.
- What got in the way
- Nothing of note for this use. Care is needed to avoid trailing-newline differences between the bytes hashed and the bytes sent, which is a silent source of mismatches.