GitLab

Bug: 3484927
Change-Id: I0360fca2adf366009a5c2ae0e6a18f4e975c481a

There was an unfinished code path to use Authenticated Attributes to
verify JAR files. This finishes it up and allows PKCS#7 signatures with
that field instead of a direct digest on the encapsulated data.

The description of Authenticated Attributes can be found in RFC 3852
section 9 referred to as "authAttrs."

Bug: 9625223
Change-Id: Ia2c8fc09d39fbb67c1bdcdfe087f185471dcedd4

Bug: 3484927
Bug: 9656330
Change-Id: I34dbf3398ed955a6c621e154a7c0e4c0b51b9ebd

Bug: 3484927
Change-Id: I6d2417e04fd65ee95160a54b08d7cd5210973354

Bug: 3484927
Change-Id: I30c30799aed1b3bbd1b2c90825685cea457600d1

Bug: 3484927
Change-Id: I5820267491b850b8fcc696fa48962710de123009

Bug: 3484927
Change-Id: I9a2702970fe746b1f6bbbb438e4ce830e916bad4

Bug: 3484927
Change-Id: I759b10ff42ebbc5849b174241fa3d9b004e10959

We really don't want to compute a new regular expression and compile
it into a new Pattern every time we call nextInt (and friends). Adding
a single-element cache (flushed if the Scanner's locale changes) makes
this 100x faster. There still exists a pathological case where you
switch back and forth between bases.

Also improve the documentation to make it clearer that you really don't
want to use this awful class anyway.

Also bring back a few more of the tests we lost in the gingerbread timeframe.

Bug: https://code.google.com/p/android/issues/detail?id=57050
Change-Id: Id6095682fb44abae2887dda29dd3d32ac777c68f

Our new getopt_long(3) distinguishes between illegal, invalid,
unrecognized, ambiguous, and unknown options; the old one only
had ambiguous and [two slight variants of] unknown.

Change-Id: Iec4f124d66e4e483292043db5a93caa4cf1a15b0

Change-Id: I4acecd936075f226ae867d8b361ff422978af7de

This adds the ability to use Application-Layer Protocol Negotiation
(ALPN) as both a client and a server. ALPN is essentially like Next
Protocol Negotiation (NPN) but negotiation is done in the clear. This
allows the use of other protocols on the same port (e.g., SPDY instead
of HTTP on port 80).

Although previously clients using NPN were able to use cut-through, the
new ALPN API does not provide for a way for a client to enable that
during a callback. So the only difference is that NPN clients can enable
SSL False Start while ALPN clients cannot currently.

Change-Id: I42ff70f3711e9cccaf754d189f76eeaa9db5f981

By being more consistent in parameter naming, we can inherit more javadoc.

Also fix a couple of javadoc warnings in KnownFailure and DataInputStream.

Change-Id: I778f40469404fb50c51cdb1068970974f923180c

Fixes a harmony-tests/src/test/java/org/apache/harmony/nio/tests/java/nio/channels/ServerSocketChannelTest
test that had been failing since we turned it back on.

Change-Id: I76cbc5edc1ab9edc4d2818bd23649f4b906d662c

There are many reasons why the initial connect(2) may have resulted
in a ConnectException, only one of which (EINPROGRESS) means we haven't
yet failed.

Bug: https://code.google.com/p/android/issues/detail?id=56684
Change-Id: I2115998bce9043f076418fb0d1c22a26e04ee2e1

This reverts commit 77579248.

Further investigation suggests this is a worse clock for our purposes, not the better one it would appear to be from the man page. It looks more like it should have been called CLOCK_TSC.

Change-Id: I6bf7fe4dac19272f145d240917129b4d5ab5ade1

We still need to use CLOCK_MONOTONIC on Darwin.

Bug: 9511688
Change-Id: Ieb1091e24ad5cd3bab79a4de1b1494cc64eef3d4

Bug: https://code.google.com/p/android/issues/detail?id=56385
Change-Id: Ie60d8c61aae09358d296654bd30378cbd11eeecb

CouncurrentHashMap was skipped from this sync.

Change-Id: I29c67698a2e706b22e3cb5920c5fe91f1f15461c

I've observed 14 failing tests both before and after
the update.

Change-Id: I40dfd9efe35ed03d89b38b030d3c7b6558b247e2