| commit | 7a55ae3ddccfe736398101a8186441b17143425a | [log] [tgz] |
|---|---|---|
| author | Seth Moore <sethmo@google.com> | Wed Jun 23 14:28:11 2021 -0700 |
| committer | Seth Moore <sethmo@google.com> | Thu Jun 24 12:45:23 2021 -0700 |
| tree | 31abb3313ec94c4ee832a6a3355599ca95368b6a | |
| parent | 5d3dd75690635b52c2d02f550d718a41273e0a43 [diff] |
Fix flaky corrupted padding tests It's possible that corrupted ciphertext decrypts just fine. e.g. the output ends with "0x01". However, the chances of this happening are relatively low (roughly 1/256). Corrupt the ciphertext up to 8 times, ensuring that the likelihood of multiple successful decryptions is so miniscule that it's effectively impossible. Test: Ran *PaddingCorrupted tests 50000 times Change-Id: If40ecd7817819921c020ea9b86ada18c4c77ea55