Add verification logic to the crypter fuzz target by decrypting the resulting ciphertext from a successful call to Encrypt() or EncryptSecret() and verifying that the output matches the original plaintext.
This ensures that the encryption/decryption cycle preserves data correctness, rather than just checking for execution crashes.
Add verification logic to the `crypter` fuzz target by decrypting
the resulting ciphertext from a successful call to `Encrypt()` or
`EncryptSecret()` and verifying that the output matches the
original plaintext.
This ensures that the encryption/decryption cycle preserves data
correctness, rather than just checking for execution crashes.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
Unsure if changes like this are needed. The oracles added are inexpensive enough to not affect fuzzing performance, and they do increase chances of catching a future regression, but there's no increase in coverage so it might be code churn after all.
Marking as draft for now.