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

Commit 8ac07435 authored by Chirag Pathak's avatar Chirag Pathak Committed by Shawn Willden
Browse files

Fix for the documentation in TimeStampToken.aidl. HMAC computation will always... 

Fix for the documentation in TimeStampToken.aidl. HMAC computation will always use 1, which is the value of SecurityLevel.TRUSTED_ENVIRONMENT. This is done for backwards compatibility purpose.
Test: N/A
Bug: None.

Change-Id: I1fd979908103f9095cc7c306e0d5036d6b357b30
parent 4477ee05

security/secureclock/aidl/android/hardware/security/secureclock/TimeStampToken.aidl

+2 −4
Original line number Diff line number Diff line
@@ -39,7 +39,7 @@ parcelable TimeStampToken { 
     * 32-byte HMAC-SHA256 of the above values, computed as:

     *

     *    HMAC(H,

     *         ISecureClock.TIME_STAMP_MAC_LABEL || challenge || timestamp || securityLevel )

     *         ISecureClock.TIME_STAMP_MAC_LABEL || challenge || timestamp || 1 )

     *

     * where:

     *
@@ -50,9 +50,7 @@ parcelable TimeStampToken { 
     *   ``||'' represents concatenation

     *

     * The representation of challenge and timestamp is as 64-bit unsigned integers in big-endian

     * order. SecurityLevel is represented as a 32-bit unsigned integer in big-endian order as

     * described in android.hardware.security.keymint.SecurityLevel. It represents the security

     * level of the secure clock environment.

     * order.  1, above, is a 32-bit unsigned integer, also big-endian.

     */

    byte[] mac;

}