Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9b7f79cb authored by Seth Moore's avatar Seth Moore
Browse files

Clean up description of IRemotelyProvisionedComponent uniqueId 

The identifier is to be used in telemetry to identify problematic
implementations. Thus, it needs to be globally consistent, at least
within a given device type.

Test: None -- doc only changes
Bug: 231495834
Change-Id: Ia55db336fa099d8e1196f6bfe2bafb6fa5ead329
Merged-In: Ia55db336fa099d8e1196f6bfe2bafb6fa5ead329
parent 74386101

security/keymint/aidl/android/hardware/security/keymint/RpcHardwareInfo.aidl

+5 −1
Original line number Diff line number Diff line
@@ -59,13 +59,17 @@ parcelable RpcHardwareInfo { 
     * client should NOT interpret the content of the identifier in any way. The client can only

     * compare identifiers to determine if two IRemotelyProvisionedComponents share the same

     * implementation. Each IRemotelyProvisionedComponent implementation must have a distinct

     * identifier from all other implementations on the same device.

     * identifier from all other implementations, and it must be consistent across all devices.

     * It's critical that this identifier not be usable to uniquely identify a specific device.

     *

     * This identifier must be consistent across reboots, as it is used to store and track

     * provisioned keys in a persistent, on-device database.

     *

     * uniqueId may not be empty, and must not be any longer than 32 characters.

     *

     * A recommended construction for this value is "[Vendor] [Component Name] [Major Version]",

     * e.g. "Google Trusty KeyMint 1".

     *

     * This field was added in API version 2.

     *

     */