| Alex Klyubin | 4d6e70b | 2016-03-31 18:56:59 -0700 | [diff] [blame] | 1 | APKs in this directory are used by PkgInstallSignatureVerificationTest. |
| Dan Cashman | 82df440 | 2018-03-27 15:19:01 -0700 | [diff] [blame] | 2 | See that class for additional information about their use. |
| Alex Klyubin | 4d6e70b | 2016-03-31 18:56:59 -0700 | [diff] [blame] | 3 | |
| Dan Cashman | 82df440 | 2018-03-27 15:19:01 -0700 | [diff] [blame] | 4 | In general, they are differently signed forms of the tinyapp APK and follow |
| 5 | the following naming scheme: |
| 6 | |
| 7 | ${version}-with-${signing-algorithm}-${OID-params}-${keysize}-${extra_info} |
| 8 | |
| 9 | where some fields may not be present, but have the following meaning: |
| 10 | |
| 11 | version: denotes which APK Signature Scheme (v1, v2, and/or v3) was used |
| 12 | signing-algorithm: indicates how the signature was generated |
| 13 | OID-params: PKI object identifiers indicating how to use the provided key |
| 14 | to generate the signature. See, e.g. rfc3279 and rfc4055. |
| 15 | keysize: the size of the key used for signing |
| 16 | extra_info: additional notes to distinguish packages. Currently this denotes |
| 17 | which test certificates were used to generate a proof-of-rotation object, |
| 18 | if one exists, included in the signing block of the APK, as well as the |
| 19 | capabilities of those certificates according to APK Signature Scheme v3. |
| 20 | |
| 21 | Generation of these apks was performed using the apksigner command-line tool, |
| 22 | which lives at tools/apksig/src/apksigner/java/com/android/apksigner/ in the |
| 23 | android source tree. Please refer to the usage instructions there for how to |
| 24 | sign APKs using different keystores, providers, etc. In particular, some of |
| 25 | the APKs in this directory were generated by modifying the apksig library (see |
| 26 | README in tools/apksig/) to create invalid or unsupported outcomes. |