| 5189c980ebdc842e0e5ca7d6794b4880aa0b6cd5 |
|
04-Oct-2012 |
Kenny Root <kroot@google.com> |
OpenSSLCipher: remove buffer for partial blocks
Some block ciphers buffer the first block used. We weren't accounting
for this so we started failing with DES3. This led to another issue that
OpenSSL can sometimes keep things in its internal buffer. Instead of
having multiple levels of buffering, just rely on OpenSSL to do the
buffering.
Change-Id: I40a6c7e92e70d3c9ae530f35e8a4234f62e8d225
|
| 46a749879a6d52408e51938b9e63683b238d0bee |
|
03-Oct-2012 |
Kenny Root <kroot@google.com> |
OpenSSLCipher: 3DES cipher name depends on key size
OpenSSL doesn't infer from the key size whether to use two-key or
three-key 3DES, so explicitly call it out.
Change-Id: Ibd93088844e7585e72a7c7857dd2af8a150b3780
|
| fe8b870db2b374e21c69c2ff0050e6a34e0d8d94 |
|
05-Sep-2012 |
Brian Carlstrom <bdc@google.com> |
Tracking upgrade to bouncycastle 1.47
Change-Id: Ie1f2ae92638e81ccd7e4ec2459199e6eecdac75f
|
| 281be77953d7827e31fc5aa0e1c29a06063f237f |
|
26-Jul-2012 |
Brian Carlstrom <bdc@google.com> |
Fix even more CipherTest flakiness due to implicit random IV values
When Cipher.init is not passed AlgorithmParameters, it will implicitly
generate what it needs, leading to random values that occasionally
caused BadPaddingException not to be thrown when expected. Disable
that behavior by explictly passing in the static IV value.
Bug: 6354967
(cherry-picked from 3441ddaa2ce320360292702dd63dad052cb6999d)
Change-Id: I38d3be7260fd28ffd47f49cb06f68d68c9c20e9f
|
| 3441ddaa2ce320360292702dd63dad052cb6999d |
|
26-Jul-2012 |
Brian Carlstrom <bdc@google.com> |
Fix even more CipherTest flakiness due to implicit random IV values
When Cipher.init is not passed AlgorithmParameters, it will implicitly
generate what it needs, leading to random values that occasionally
caused BadPaddingException not to be thrown when expected. Disable
that behavior by explictly passing in the static IV value.
Bug: 6354967
Change-Id: I804c7e30e1c29b92780a9b6271c35505835d58f5
|
| d77eccc93cbf92c400ebd114ea8e91413b882d69 |
|
25-Jul-2012 |
Brian Carlstrom <bdc@google.com> |
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
|
| f19b9c467fb584a79463357e160c0a41c80d05c8 |
|
25-Jul-2012 |
Brian Carlstrom <bdc@google.com> |
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
Change-Id: Ia4e53973da05377687faf327b64acd42a2db344a
|
| 459a8ccbcc3dfde730780244e2122a734858acee |
|
19-Jul-2012 |
Brian Carlstrom <bdc@google.com> |
Address flakiness of doFinal and unwrap CipherTests
The tests occasionally did not throw BadPaddingException when
expected. This seems to be because in those cases the random generated
keys were creating cipher text that appeared to be correctly PKCS#5
padded. In reproducing this in the doFinal case, this happened within
a few hundred runs.
Bug: 6301793
Change-Id: Ibd2d9bdd2fe88bccb20089ef653763849f45ff4c
|
| 2ac3f4de596bdeea397e25692b4a4f5a6c15426f |
|
19-Jul-2012 |
Brian Carlstrom <bdc@google.com> |
Address flakiness of doFinal and unwrap CipherTests
The tests occasionally did not throw BadPaddingException when
expected. This seems to be because in those cases the random generated
keys were creating cipher text that appeared to be correctly PKCS#5
padded. In reproducing this in the doFinal case, this happened within
a few hundred runs.
Bug: 6301793
Change-Id: Ibd2d9bdd2fe88bccb20089ef653763849f45ff4c
|
| 937b6c4ef5f8ad57279e2ebed4393a78d1729d8b |
|
28-Jan-2011 |
Brian Carlstrom <bdc@google.com> |
Tolerate leading slash in Cipher transformation
Bug: 3387688
Change-Id: Icd551df2cafd256e49fb92d12d7cb381479d841d
|
| 6e65088f21ac5bda5d25fade13ee360c5cba3457 |
|
25-Sep-2010 |
Jesse Wilson <jessewilson@google.com> |
Rely on the test runner to ensure a pristine VM.
Change-Id: I6f5bfad6f861eb7b398ed7d86747d66cea4f2343
http://b/issue?id=2660429
|
| f33eae7e84eb6d3b0f4e86b59605bb3de73009f3 |
|
13-May-2010 |
Elliott Hughes <enh@google.com> |
Remove all trailing whitespace from the dalvik team-maintained parts of libcore.
Gentlemen, you may now set your editors to "strip trailing whitespace"...
Change-Id: I85b2f6c80e5fbef1af6cab11789790b078c11b1b
|
| cec4dd4b1d33f78997603d0f89c0d0e56e64dbcd |
|
26-Apr-2010 |
Peter Hallam <peterhal@google.com> |
merge more modules into luni
|