Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Clarify PackageManager.hasSigningCertificate docs." into pi-dev

Browse Source 
am: a5bdeabf15

Change-Id: Iae114b67cfdda3ad043cbd33076a74879575a2c1
This commit is contained in:
Daniel Cashman
2018-04-09 16:18:13 -07:00
committed by android-build-merger
parent 5f81832b4f a5bdeabf15
commit 9b1bd200b2
1 changed files with 13 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
core/java/android/content/pm/PackageManager.java
View File

@@ -6131,7 +6131,9 @@ public abstract class PackageManager {
* signed. This should be used instead of {@code getPackageInfo} with {@code GET_SIGNATURES}
* since it takes into account the possibility of signing certificate rotation, except in the
* case of packages that are signed by multiple certificates, for which signing certificate
* rotation is not supported.
* rotation is not supported. This method is analogous to using {@code getPackageInfo} with
* {@code GET_SIGNING_CERTIFICATES} and then searching through the resulting {@code
* signingCertificateHistory} field to see if the desired certificate is present.
*
* @param packageName package whose signing certificates to check
* @param certificate signing certificate for which to search
@@ -6145,13 +6147,19 @@ public abstract class PackageManager {
}
/**
* Searches the set of signing certificates by which the given uid has proven to have been
* signed. This should be used instead of {@code getPackageInfo} with {@code GET_SIGNATURES}
* Searches the set of signing certificates by which the package(s) for the given uid has proven
* to have been signed. For multiple packages sharing the same uid, this will return the
* signing certificates found in the signing history of the "newest" package, where "newest"
* indicates the package with the newest signing certificate in the shared uid group. This
* method should be used instead of {@code getPackageInfo} with {@code GET_SIGNATURES}
* since it takes into account the possibility of signing certificate rotation, except in the
* case of packages that are signed by multiple certificates, for which signing certificate
* rotation is not supported.
* rotation is not supported. This method is analogous to using {@code getPackagesForUid}
* followed by {@code getPackageInfo} with {@code GET_SIGNING_CERTIFICATES}, selecting the
* {@code PackageInfo} of the newest-signed bpackage , and finally searching through the
* resulting {@code signingCertificateHistory} field to see if the desired certificate is there.
*
* @param uid package whose signing certificates to check
* @param uid uid whose signing certificates to check
* @param certificate signing certificate for which to search
* @param type representation of the {@code certificate}
* @return true if this package was or is signed by exactly the certificate {@code certificate}