| 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/x509/X509V3CertificateGenerator.java
|
| 7dad97b63c47edea4e3afb374dcd00c7b7a1bdd4 |
|
04-Jan-2017 |
Sergio Giro <sgiro@google.com> |
bouncycastle: upgrade to version 1.56
Merge remote-tracking branch 'aosp/upstream-master' into merge-to-156
Test: ran the following cts modules: CtsLibcoreFileIOTestCases CtsLibcoreJavaUtilCollectionsTestCases CtsLibcoreJsr166TestCases CtsLibcoreLegacy22TestCases CtsLibcoreOjTestCases CtsLibcoreOkHttpTestCases CtsLibcoreTestCases
Bug: 31076342
Change-Id: Iceb926dc5a312b2047bf19d1c82fb16e42bc1461
|
| 4caba4cfca3316673ae4e330e8a47932bed8a53a |
|
28-Dec-2016 |
Sergio Giro <sgiro@google.com> |
bouncycastle: Android tree with upstream code for version 1.56
Test: no tests needed, this branch is for easy diffing against upstream
Change-Id: Ib75613e1211e7f02f225b9020ba31f2b45acc8d8
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/x509/X509V3CertificateGenerator.java
|
| c415feea05de0907cf741293bd538bd10d3194c6 |
|
09-Sep-2016 |
Sergio Giro <sgiro@google.com> |
X509V3CertificateGenerator: use a X509CertificateObject from a different package
Use org.bouncycastle.jcajce.provider.asymmetric.x509.X509CertificateObject
instead of org.bouncycastle.jce.provider.X509CertificateObject.
These classes serve the same purpose, the latter is kept by BouncyCastle
only in case developers have serialized instances. The former is better as
it uses the more up-to-date hash equivalent to that of Java 8.
In Java 8, the hash code in the abstract class Certificate was changed.
This led TrustedCertificateStore#testMultipleIssuers to fail as it uses
HashSets for comparison and org.bouncycastle.jce.provider.X509CertificateObject
was still using the old definition (while conscrypt generated ones use the
ones in the abstract class). After this commit the certificate generator
uses a more up-to-date version of the class, in which the hash coincides
with the one in Java 8 and the test now passes and everything's great.
Bug: 31287348
Test: old-cts run cts --class com.android.org.conscrypt.TrustedCertificateStoreTest
Change-Id: I4e373380f8a3e669cfcdf8ce7386f58e559c0c16
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/x509/X509V3CertificateGenerator.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/x509/X509V3CertificateGenerator.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/x509/X509V3CertificateGenerator.java
|
| d001700a15b8bd733ae344c1fc315b97c43c6590 |
|
28-Jul-2014 |
Kenny Root <kroot@google.com> |
Upgrade to 1.51
f98b02ab394044a3c237d2c7a2ee5ef65793e8e9 bcpkix-jdk15on-151.tar.gz
95e59ad2492598d729cfc559b480c3f172de5dc3 bcprov-jdk15on-151.tar.gz
Bug: 16578237
Change-Id: Ie4a3cd01b52b504a1098b00b413f1418273a6ef2
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/x509/X509V3CertificateGenerator.java
|
| 70c8287138e69a98c2f950036f9f703ee37228c8 |
|
31-Jan-2013 |
Brian Carlstrom <bdc@google.com> |
bouncycastle 1.48 upgrade
(cherry-picked from e1142c149e244797ce73b0e7fad40816e447a817)
Change-Id: Idb04baf42de07b18ddb162e5cd1f98cdadf366f4
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/x509/X509V3CertificateGenerator.java
|
| e6bf3e8dfa2804891a82075cb469b736321b4827 |
|
18-Sep-2012 |
Brian Carlstrom <bdc@google.com> |
Make existing bouncycastle bcprov build on host and add host-only bcpkix build
- Move existing provider source to bcprov
- Added bcpkix host build to support built/tooks/signapk
sha1sum of sources:
- 10bfea344842fe8e065c80e399c93f8651dc87d8 bcprov-jdk15on-147.tar.gz
- 913828c7ae36e030508e97e07b3c213fb1db1e9c bcpkix-jdk15on-147.tar.gz
Bug: 7056297
Change-Id: Id4f957f300a39aa34b4c3c679b2312631d3f1639
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/x509/X509V3CertificateGenerator.java
|