com.android.remoteprovisioner Copy

The RemoteProvisioner app from the Android Open Source Project, the pre-Android 14 app half of Remote Key Provisioning (RKP). AOSP describes the older design in these words: "Before Android 14, RKP was separated into an app, RemoteProvisioner, and Keystore 2.0. The RemoteProvisioner app was responsible for contacting the RKP backend, and Keystore 2.0 was responsible for both storing the keys and communicating with HALs." The Android 13 release manifest for the project declares the package name com.android.remoteprovisioner, a boot receiver, a PeriodicProvisioner job service and an exported GenerateRkpKeyService, and requests the internet, network state and boot completed permissions. It declares no launcher activity in that manifest. Version note: this package name belongs to Android 12 and 13. AOSP states that RKP "has been a part of AOSP since Android 12" and that "Android 14 introduces a remote provisioning updatable module", with the RKP Mainline APEX, com.android.rkpd, containing "the Remote Key Provisioning Daemon (RKPD) application and a remote provisioning system server component". The AOSP project's release branches run from android12-release to android13-qpr3-release and no later release branch is listed. That lines up with this site's sample, where the package is recorded on API levels 31 to 33 and not above. Where this site holds signer data, which is 4 of the 8 makes in the sample (Google, Motorola, SMT_HK and Xiaomi), it is signed by a Google key on the Google device and by that maker's own OEM key on the other three. On Android 14 and later the equivalent component is the RKPD app, documented separately on this site as com.android.rkpdapp and com.google.android.rkpdapp. For Android Enterprise, EMM and kiosk fleets this is security plumbing rather than a feature, and no management role is identified in the sources cited here. Whether a particular Android 12 or 13 device depends on remotely provisioned attestation keys rather than factory-provisioned ones could not be established from these sources. On a device that does, disabling the app AOSP names as responsible for contacting the RKP backend would be expected to interfere with obtaining attestation certificates, and no benefit of disabling it was found, so it is best left in place.

• Remote Key Provisioning - Android Open Source Project →
• RemoteProvisioner AndroidManifest.xml (android13-release) - Android Open Source Project →
• platform/packages/apps/RemoteProvisioner branches and tags - Git at Google →
• Package provenance for com.android.remoteprovisioner - Android System App Database →

• Re-signed by each device maker with its own platform key - 4 different certificates appear across 3 device makers in our sample. That is the signature of a stock AOSP/system package every OEM builds and signs itself, not a single maker's or a third party's preinstall.
• Its largest observed manifest declares 6 permissions: 5 install-time and 1 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.