2ae508725e0b6c4dd4c23717bc1625bd745670b6 |
|
02-Jun-2015 |
Sergio Giro <sgiro@google.com> |
libcore: throw InvalidKeyException instead of ProviderException In java.security javax.crypto and java.security classes with late binding, when guessing the provider and none of the available ones supports the specified key Bug: 18987633 (cherry pick from e38b83dd96281d178b01476b67d354655bf2de62) Change-Id: I5931046e9044984baf724157138bf3a7c7ef5e90
|
e38b83dd96281d178b01476b67d354655bf2de62 |
|
02-Jun-2015 |
Sergio Giro <sgiro@google.com> |
libcore: throw InvalidKeyException instead of ProviderException In java.security javax.crypto and java.security classes with late binding, when guessing the provider and none of the available ones supports the specified key Bug: 18987633 Change-Id: I2a4d258c8f628e2c40f4cbb060cb8825097bd22a
|
20e310656f03cd83355eae5cd25237f71b80341a |
|
13-Mar-2015 |
Kenny Root <kroot@google.com> |
Late binding: specified Provider forces its use If a Provider is specified in a call to Signature#getInstance, Cipher#getInstance, KeyAgreement#getInstance, or Mac#getInstance, it should return that provider no matter if the properties on that provider say it should support it. Bug: 19730263 Change-Id: I56045e4cb470a0e1aa0e108a443e04043467c475
|