| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
after importing for verification/debugging"
Merge commit '3d82ade7a9b764695bad89d2476a73441118411b' into dalvik-dev
* commit '3d82ade7a9b764695bad89d2476a73441118411b':
Have certimport.sh list certificates in BKS keystore after importing for verification/debugging
|
| | |
| |
| |
| |
| |
| | |
verification/debugging
Change-Id: Ic336f10d96bbf93b1dc5cfd8b64a4c9eaa4f3a68
|
| |/
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
- TC TrustCenter Class 2 CA II
- TC TrustCenter Universal CA I
|
| |
|
|
| |
- 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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
QuoVadis Root Certification Authority
QuoVadis Root CA 2
QuoVadis Root CA 3
|
| | |
|
| | |
|
| | |
|
| |
|
