| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| | |
Bug: https://code.google.com/p/android/issues/detail?id=54580
Change-Id: Ib41f9fe06b34761f2be59622cbe8a05858551e5b
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
OpenSSLProvider is the default provider now so there's no reason to
request it by default.
Change-Id: I03cd947072226d7a58de94cb2c116d7049918bbd
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | | |
Change-Id: I8fecdc55b2cf0041ceed643eb48df53d22ecd600
|
| |/
|/|
| |
| |
| |
| |
| | |
44021512997b337e6079e46fd4230ce979c20b6f
Bug: 8685209
Change-Id: I8516bee529cfc6396c3512d3c2db04ebaee2d712
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: Id296613590f7ccfc7b5880b27418fe3f5d511974
|
|/
|
|
|
|
|
|
| |
I fear this is just the start for this code. There seem to be a lot
of assumptions about the types used by OpenSSL that may not hold for
a 64-bit build.
Change-Id: I05c276ff06adc66c1e7878196ce1afd5fba290d9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
icu4c doesn't translate the deprecated language codes Java uses back into
the current language codes, so we need to do that ourselves.
Bug: 8619221
Change-Id: I241c33e10547d2858ac08e303d5f0327912a89ff
|
|/
|
|
|
|
| |
Bug: 8313312
Bug: https://code.google.com/p/android/issues/detail?id=52295
Change-Id: I1fa31335de9c9ee002c25869dbaa2574c70f48cf
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: http://code.google.com/p/android/issues/detail?id=21531
Bug: 5580664
Change-Id: I19b432bc84468828258cbcd44266e4b712e6175d
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OpenSSL won't generate primes smaller than 16 bits, so do it ourselves
roughly the same way they would.
Also remove pure duplicate tests from OldBigIntegerTest, and add some
new tests to the modern BigIntegerTest.
Change-Id: I3000942a7a4f2359d5cbe28795b4f8dd96715ef8
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: 8605629
Change-Id: I45a5db6a9a216e5be13e122b0fd0bcde25f121d8
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
X.509 does not have a notion of milliseconds so it was not being set
through the Calendar instances we used in OpenSSLX509Certificate, et al.
Instead it was getting whatever the current millisecond offset was from
the GregorianCalendar default constructor. That made two parsed
certificates unlikely to be equal when comparing since the milliseconds
were also checked.
(cherry picked from commit 3725893865ddbdd2e9cebc2ea2f7ecfc357fcfbb)
Bug: 8616647
Change-Id: Ia914856a560526718957607d69401eab8c2830cf
|
|/
|
|
|
|
|
|
|
|
|
| |
The new AndroidKeyStore uses a KeyPairGenerator which uses a special
algorithm parameters. The libcore test doesn't know about those at
compile time. It is tested elsewhere in the CTS tests.
(cherry picked from commit e60ba6238d887eb7c4882cccf375b445ebf4c10d)
Bug: 8704815
Change-Id: I855e3f11d154335145e047f33920eba00993fb7a
|
|
|
|
|
|
|
|
| |
The code samples for the various "hour of day" format specifiers
were wrong.
Bug: https://code.google.com/p/android/issues/detail?id=53983
Change-Id: Idc9cab93fbba62cd6dce874cc1d0f5908a351c8b
|
|
|
|
|
| |
Bug: https://code.google.com/p/android/issues/detail?id=53983
Change-Id: I005c73f168ac39ba72b93f78ec70460f428295fb
|
|
|
|
|
|
|
|
|
|
|
| |
documentation.
Also do some other documentation clean-up. In particular, it's confusing
to use ^ to mean exponentiation when the language uses it to mean
exclusive-or.
Bug: https://code.google.com/p/android/issues/detail?id=54103
Change-Id: I34871b05a986e97c814dc0a060872bda6c68d031
|
|
|
|
| |
Change-Id: I04c1957955fc8cf9af9374264a0266ad61334795
|
|
|
|
|
|
|
|
| |
We were hitting a couple of OpenSSL bugs. I've reported them upstream, and
work around them in the meantime.
Bug: 2943474
Change-Id: Ia06bcf3025f525a954d9b918669d09531631a266
|
|
|
|
|
|
| |
This reverts commit 7653089cb7609f6269aecd68e839c40941cb1a46
Change-Id: Ie3c0fd1f5d51d61e55ec3a581464943e63716b38
|
|
|
|
|
|
| |
This reverts commit a77a6f93de75a1d9c51ea142013c5fd54c85a359
Change-Id: If6cfe5031efd2d36eae4af5774757667efcb67a2
|
|
|
|
| |
Change-Id: I4b85c2419e73dc15f921157ce3221225a06b30bf
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also to prevent similar problems in the future, remember SSLSession we
are trying to use in case it disappears from SSLSessionContext.
Added test of SSLSocket SSLSession reuse.
Bug: https://code.google.com/p/android/issues/detail?id=52738
Bug: 8313208
Change-Id: I30824cdf96a0d1086abccb61c011dbc9ad60f8cf
|
|
|
|
|
|
|
| |
BUG=https://code.google.com/p/chromium/issues/detail?id=167607 and
https://b.corp.google.com/issue?id=7920492
Change-Id: Ib917c3a4a8ea6a12f685c44056aa44aa414d45e6
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ic4acfcf8553e0108e6ad127afa2745bb551acba3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also add a generic fallback for certificate verification when the specific
type of error is unknown.
Bug: 8550441
Change-Id: Iee44be55c698a4a33450b569c12199747fdbcc49
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's no need for the OpenSSL-backed KeyFactory.translateKey to
create copies of Key instances which are already backed by OpenSSL.
Change-Id: I9411d774453251973703ba9de4fd413fac4b2183
|
|\ \ \
| | | |
| | | |
| | | | |
behavior."
|
| | |/
| |/|
| | |
| | |
| | | |
Bug: 8541850
Change-Id: I8843aeee25eeefe0f6d5e16dd359ba78ef5a01cc
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Id724b75dd78b68ed00f5db4989c4070896996ec0
|
|/ / /
| | |
| | |
| | |
| | | |
Bug: 8476102
Change-Id: I764c2aec944558129c8ac04ee0593fb3de82870e
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should be covered by NativeCryptoTest as well but there was a missing
native function that caused
tests.security.cert.CertificateCertificateRepTest#testReadResolve
to fail.
There was also a missing OpenSSL error catch that made the same test
fail.
Bug: 8488314
Change-Id: Ic8bca86ab221a478e303c8e94662f28d279c19b6
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Should be throwing CertificateException when InputStream is null.
Sometimes OpenSSL doesn't push an error onto the list when PEM encoding
fails. This can be seen with the call to PEM_read_bio_X509 with
hyts_badpem.cer Throw a generic RuntimeException instead.
Bug: 8488314
Change-Id: Iee3b240e3def076f67e15980897be87ff3bf5e6c
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
OpenSSL checks KeyUsage for "Certificate Signing" when checking for a
CA, but Java just specifies that the getBasicConstraints call only looks
at the BasicConstraints itself.
Bug: 8488314
Change-Id: I072cd2e9f1a9295a717f7587817149200113c65f
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
generateCertPath, generateCertificates, and generateCRLs have slightly
different behavior on null input. Match the RI and (apparently) previous
BC behavior.
Bug: 8488314
Change-Id: I7a175815adb77b38783860806ddff93eaef521d2
|
|/ /
| |
| |
| |
| |
| | |
This allows the code to be used on 64-bit platforms.
Change-Id: I1c42d48696296f74135cd209b3042b8973779e40
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
OpenSSL KeyFactory.translateKey encapsulates all the functionality
for translating arbitrary Key instances to OpenSSL-backed Key
instances. Thus, there's no need to replicate that functionality
elsewhere.
Change-Id: I4caa0021e51a83be6932617117275fd033b6d5f7
|
|/
|
|
|
|
|
|
|
| |
This fixes the bug where OpenSSL-backed KeyFactory instances (RSA,
DSA, EC) could translateKey from PrivateKey to PublicKey and vice
versa when presented with "opaque" keys whose translation is
performed via their primary encoded form.
Change-Id: Ia24a2591a06ac82c5225a3a9e3069af7a01a0c37
|