GitLab

* changes:
  X509CertificateTest: test for empty subjectAltNames
  Track Bouncycastle fixes for subjectAltNames

If the subjectAltNames field is missing, providers should return null

Change-Id: If11202d97e0a5a41ca598fb7df3320d6a20474c9

Change-Id: Ib67395e8ec461feb8f4b1826d18e98d318a157d2

In SubjectAlternativeName, the directoryName (4) entry is actually a
CHOICE of a single possibility. Harmony was trying to decode it as the
single possibility itself and running into parsing issues.

Additionally, change T61String (TeletexString) handling to assume UTF8
encoding like the RI does.

Change-Id: Ic0b9541dfed21b59940fa50a27cee2e7704d8950

The RI and other providers will ignore invalid IP lengths instead of
throwing a parsing exception. Bring Harmony in line with those other
providers.

Change-Id: I65715a58614543ab296493829338239cf402ae5d

If an RSA field is left NULL, it will not be represented in the ASN.1
output of the RSAPrivateKey. This leads to problems trying to recreate
the key since it does not emit the NULL fields and the fields are not
numbered.

Bug: 7920357
Change-Id: I144302925f9b080a2152a6d12f77981b3aad9495

The docs say that if an InputStream does not have any certificates, it
will return an empty collection.

Change-Id: I470c05c097de6c3fa80571294b31cf7ffd10f003

This reverts a regression introduced in commit 1331404b
that was caught by tests.api.javax.net.ssl.HostnameVerifierTest.testVerify

Bug: 7894348
Bug: http://code.google.com/p/android/issues/detail?id=41662
Change-Id: Iec8000b716e3d99ca7af4aa2c3fd7b43e22c68cd

Serializing and deserializing should work for X509Certificate

Change-Id: Id32df1a50e25e48194702744dce6b9be4fd6929d

This is a minor cleanup after
  https://android-review.googlesource.com/47964

Change-Id: Id8de6c09f3397b044082c275095ff7a7a43185f9

Bug: 7894348
Bug: http://code.google.com/p/android/issues/detail?id=41662
Change-Id: I3814d653b628f6af12ce1ba59b39b1c7cc45e124

There were a few other instances of the same error reported in the bug,
plus bits that didn't make much sense, so I gave the whole file a quick
scrub.

Bug: http://code.google.com/p/android/issues/detail?id=42100
Change-Id: I40669a614c92a80038253a4adf89f8c7f7f8e95c

Bug: http://code.google.com/p/android/issues/detail?id=42059
Change-Id: I08112426fcd8a2389e4068d2c6f9c3a583ec95d5

Make sure that generateCertificate and generateCertificates end at the
right point when using a stream supporting mark and reset.

The support for this seems spotty at best. Various implementations have
broken support in different parts.

Change-Id: Ib8a3f7c451adca4e05fcb3e8409e93c319557497

Change-Id: I461881d515201829eae08046574824dbda30d460

Change-Id: I551d6ea887e06481a3eaefec980a728a8c4191f7

Change-Id: I678a8b89d0514c270ce0ee57057cfaadf3b47543

Templatize all the OpenSSL ASN.1 type conversions to jbyteArray. Further
changes will need to use more i2d_<type> and it's all boiler-plate code.

Change-Id: Ib9c715c5c9d8b69eca6950c03e925d7e1d625cdb

Bug: 7896159
Bug: http://code.google.com/p/android/issues/detail?id=34416
Change-Id: Id1225a353b52c50bb3eedfd48e92ec85dd60134b

Change-Id: I5d1ba078b0f8f9ec8e2950e0da02481e8162a5e6