| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
These were clearly added just to shut up our own warning, and are now
unnecessary and misleading to future maintainers.
There's one barely-related change: InputStreamReader and OutputStreamWriter
are very similar, and this patch makes them more similar, and adds a few
missing modifiers from their fields.
Change-Id: I959011f914ff215e92bbfa41c1bac66465803685
|
|
|
|
|
|
|
| |
I've fixed a few typos, and removed a few of the more egregiously nonsensical
or incorrect comments that were nearby.
Change-Id: I35851baebd532f949cc269f4738a26eeb9b6e697
|
|
|
|
|
|
|
|
|
| |
hku had some questions about the meaning of the filenames in
cacerts. ngm responded so I captured the knowledge in the
certimport.sh for future reference so we can continue to follow the
convention.
Change-Id: I79b4ed333e541f09d60143f785e5b10d3f5e60f4
|
|
|
|
|
|
| |
(This doesn't include libcore/xml/ because I don't want to get in the way there.)
Change-Id: I46f638105d26e82d09128fca605117322229e146
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
installation (and add 1.6 JDK to PATH)"
Merge commit 'a536d01c1c0119322d655a9ec35665a36abbed6d' into dalvik-dev
* commit 'a536d01c1c0119322d655a9ec35665a36abbed6d':
Fix certimport.sh to check for Bouncy Castle provider installation (and add 1.6 JDK to PATH)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1.6 JDK to PATH)
Now if certimport.sh is run on a machine without the
BouncyCastleProvider installed, it will suggest how to apt-get install
the proper package.
At enh's suggestion, I tried running with out own local Bouncy Castle
classes to see what would happen, but the code ended up depending on
our NativeCrypto JNI code and there that isn't proper JNI code to be
loading into a RI JDK.
Also at enh's suggestion, we now prepend a JDK 1.6 bin directory to
the path for correctly correct default behavior. I do make sure it
exists and warn if it does not.
Change-Id: Ic936a6cc69fa3795e917c052ed79d19b2e66b5a1
|
|\ \
| |/
| |
| |
| | |
Conflicts:
libcore/JavaLibrary.mk
|
| |\
| | |
| | |
| | | |
TrustCenter Universal CA I"
|
| | |
| | |
| | |
| | |
| | | |
- TC TrustCenter Class 2 CA II
- TC TrustCenter Universal CA I
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I started off with a mission to remove uses of dalvik.annotation.* (stuff
like @TestTargetNew and other useless junk that just makes it harder to
stay in sync with upstream). I wrote a script to go through tests showing
me the diff between what we have and what upstream has, thinking that in
cases where upstream has also added tests, I may as well pull them in at
the same time...
...but I didn't realize how close we were to having dx fill its 1.5GiB heap.
After trying various alternatives, I decided to bite the bullet and break
core-tests up into one .jar per module. This adds parallelism back into this,
the slowest part of our build. (I can do even better, but I'll do that in a
separate patch, preferably after we've merged recent changes from master.)
Only a couple of dependencies were problematic: the worthless TestSuiteFactory
which already contained a comment suggesting we get rid of it, and the fact
that some tests -- most notably the concurrent ones -- also contained main
methods that started the JUnit tty-based TestRunner.
(In the long run, we want to be running the harmony tests directly from a
pristine "svn co" of upstream, using DalvikRunner. But this will be a big
help in the meantime, and starts the work of getting our current copy of
the tests into a state where we can start to extract any meaningful
changes/additions we've made.)
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
as known failures." into eclair
Merge commit 'ffea5cebcb45bb58d61b903f4e04c45f48442c86'
* commit 'ffea5cebcb45bb58d61b903f4e04c45f48442c86':
Mark libcore cert tests using expired certs as known failures.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug 2322662
Change-Id: If35a5a75f664535bd4eb97cf11a6afe5b0e5b4a9
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| | |
- Free SSL Certification Authority
|
| |
| |
| |
| |
| | |
- IPS SERVIDORES/emailAddress=ips@mail.ips.es
- Secure Server Certification Authority
|
| |
| |
| |
| |
| | |
- StartCom Certification Authority
- StartCom Extended Validation Server CA
|
| |
| |
| |
| |
| | |
- VeriSign Class 3 Extended Validation SSL SGC CA
- VeriSign Class 3 Public Primary Certification Authority - G5
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Merge commit 'e732bb040be84bd2ac652ca53330b80367a65725'
* commit 'e732bb040be84bd2ac652ca53330b80367a65725':
Fix browser crashes if server certificates have > 32 subjectAltNames.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Android-only changes added an arbitrary limit that upstream doesn't have.
This limit-free implementation is still more efficient than upstream (which
always allocates three Vectors).
Dr No: danfuzz
Bug: 2281869
|
| | |
|
| |
| |
| |
| | |
This replaces PrefsTester and is more general purpose.
|
| |
| |
| |
| | |
See bug 2183132.
|
| |
| |
| |
| | |
Work around apicheck bug.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Squashed commit of the following:
commit e3083dde77b71fa817c8a52d9edafcb6325cfc25
Author: Elliott Hughes <enh@google.com>
Date: Fri Oct 9 13:10:11 2009 -0700
security_dalvik
commit 0fc0101e5dbfb3e3044702579ab8087a4e07984a
Author: Elliott Hughes <enh@google.com>
Date: Fri Oct 9 13:09:48 2009 -0700
security_527399
|
|/
|
|
|
|
| |
Also rewriting SupportExec to use ProcessBuilder rather
than Runtime.exec(). Changed callers to use the ProcessBuilder
directly rather than calling-through chained methods.
|
|\
| |
| |
| |
| | |
* changes:
Replaced an O(N) algorithm with an O(1) algorithm. This shaves off 2/3 of the server cert checking time or ~200ms on Sapphire. This is in preparation for tripling the number of certs in an upcoming change.
|
| |
| |
| |
| | |
the server cert checking time or ~200ms on Sapphire. This is in preparation for tripling the number of certs in an upcoming change.
|
|/ |
|
| |
|
| |
|
|
|
|
| |
used to be an O(N) operation. If the trust anchor we're looking for was close to N, finding it could take a couple seconds. This change makes the operation O(1).
|
| |
|
|
|
|
|
|
| |
QuoVadis Root Certification Authority
QuoVadis Root CA 2
QuoVadis Root CA 3
|
|
|
|
|
|
|
| |
Since ClassLoader.isAncestorOf has been fixed these tests now succeed.
So they can be reactivated.
BUG=1732214
|
|
|
|
|
|
|
|
| |
don't work properly in the CTS environment for
some reason.
BUG=1285921
Automated import of CL 148447
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the CTS, but worked fine in run-core-tests:
- One cert test needs isolation, because
it destroys the security provider.
- The Thread.sleep() tests were too flaky.
- Tests that tried to open a temporary DEX
file failed in the CTS because we do not
have access to the system DEX cache. We
are now simply creating our own.
The Java plan in the CTS should now pass
fully. Yippie!
BUG=1285921
Automated import of CL 147896
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
core tests work better in the CTS
environment. Some tests had to be
marked broken either because they
either expose different behavior
than in run-core-tests or they
take too much time (beyond the
CTS' timeout).
BUG=1285921
Automated import of CL 147838
|
|
|
|
|
|
|
| |
Some tests are still failing in the cts host environment. This CL fixes most of them in the security module
BUG=1285921
Automated import of CL 147660
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some need to be marked broken, because
they take too long (or even forever) due
to implementation problems. Some need
to take into account differences between
the CTS environment and the Dalvik VM,
so they succeed in both cases.
BUG=1285921
Automated import of CL 147464
|
|
|
|
|
|
| |
BUG=1285921
Automated import of CL 145288
|
|
|
|
|
|
|
| |
adding lots of missing headers in the process).
BUG=1285921
Automated import of CL 143458
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|