| 6b5b8b2f1e184da74aa4b2d083cb3f6a3c227844 |
|
28-Nov-2017 |
Adam Vartanian <flooey@google.com> |
Have BC use default provider rather than always BC
In cases where BC algorithms need access to other algorithms, switch to
using the default implementation of JCA algorithms rather than always
using the BC version. Some non-deprecated BC algorithms can access
deprecated BC implementations by using this scheme, and in general we want
to use Conscrypt algorithms when available.
Also comment out a class that isn't ever used.
Bug: 68057944
Test: cts -m CtsLibcoreTestCases
Test: cts -m CtsKeystoreTestCases
Change-Id: Iec4f395b0c6c59865ff6179a4edd3124d2967da9
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/jcajce/provider/symmetric/DES.java
|
| 4936950820c68699a4ace55a2a8e5f7f677a913d |
|
11-Jul-2017 |
Adam Vartanian <flooey@google.com> |
Update change markers in external/bouncycastle.
For the most part, this is just changing markers that had no explanatory
text and adding an explanation. Some more detail on two of the common
explanations:
"Unsupported algorithms": We choose not to ship a whole lot of the
various crypto algorithms that Bouncy Castle supports. Justfying each
individual choice to disable a given algorithm is out of place in the
code and also doesn't have a natural home (since each algorithm is
disabled in upwards of a dozen places), so just mark where algorithms
are disabled due to being unsupported.
"Unknown reason": I looked in the history and couldn't find any
justification for the change. Generally these changes were made in
commits with descriptions like "bouncycastle 1.49 upgrade" from multiple
years ago. I don't want to change behavior in this change, so I left
these changes as they were; these can be revisited in the future if
desired.
This change also reverts some diffs from upstream, both inside disabled
blocks of code (which is irrelevant) and ones that are active but have
no behavioral change (for example, an added package-visible constructor
that isn't called by any class in the package). There're also a number
of whitespace-only changes that revert diffs from upstream.
Bug: 63092064
Test: cts -m CtsLibcoreTestCases
Change-Id: I27c61063eda849455bc93edaf180acefb5eed217
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/jcajce/provider/symmetric/DES.java
|
| 4a2d5c40ffefaaa02c656a091f33fecdf8592607 |
|
05-Feb-2016 |
Sergio Giro <sgiro@google.com> |
bouncycastle: upgrade to version 1.54
Merge remote-tracking branch 'aosp/upstream-master'
Change-Id: I013a531855191a4fb041f7def092704d48188bc4
|
| bdb7b3d37025690a0434040b4e0d0623d9fa74af |
|
02-Feb-2016 |
Sergio Giro <sgiro@google.com> |
bouncycastle: Android tree with upstream code for version 1.54
Change-Id: I3958e32dd005cfb37985a6f13e2464a872290658
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/jcajce/provider/symmetric/DES.java
|
| c1040cb5656c3299f1c2d0fe0bd7c44b10466aaf |
|
01-Feb-2016 |
Sergio Giro <sgiro@google.com> |
Restoring the contents of aosp after
https://android-review.git.corp.google.com/#/c/199871
git diff 9b30eb05e5be69d51881a0d1b31e503e97acd784
(ToT before submitting the patch above)
doesn't show any differences
Change-Id: I9f424a67094839f1893a23cd46ec7d6f0992ac26
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/jcajce/provider/symmetric/DES.java
|
| 53b61f9fe9d58034fcc7021137e92460f91b70ce |
|
01-Feb-2016 |
Sergio Giro <sgiro@google.com> |
bouncycastle: Android tree with upstream code for version 1.52
Android tree as of
1af9aad12fedf1d93333e19f5ed0ab86f1cc4e2a
Change-Id: I714fa0954a5d000cd88d1fb78b0b7fe28246d404
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/jcajce/provider/symmetric/DES.java
|
| 16f9ee464b68937f45d009d9c1b0eb9b544a8dee |
|
11-Dec-2015 |
Sergio Giro <sgiro@google.com> |
bouncycastle: Android tree with upstream code for version 1.49
Android tree as of 08e455bd61ddaa02255383e85480b0d9cde6e954
Change-Id: I99dab80b49707f0fdefb67ccd1bcfe765363b5e5
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/jcajce/provider/symmetric/DES.java
|