Address more CipherTest flakiness due to random IV values
In a recent change, we stopped generating random keys to prevent
flakiness in the BadPaddingException test cases. This change removes
the use of random initialization vector (IV) values. There still are
uses of SecureRandom where the API being tested requires it, but I
visually checked that none of the BadPaddingException cases fall in
this category.
Bug: 6873673
(cherry-picked from f19b9c467fb584a79463357e160c0a41c80d05c8)
Change-Id: Id09c322683972751e326569485330c23051ccf0c
1 file changed