[Android GMS 認證] keystore/keymaster/Attestation的問題

首先肯定寫入key,操做以下:android

檢查 /persist/data/sfs 目錄下是否有key文件存在     adb shell ls -la /persist/data/sfsshell

作過key provision的機器從新寫key,參照以下步驟:     1)燒userdebug版本,從新寫key須要在userdebug版本上才能作     2)執行下面命令擦除rpmb分區          MODEL1:/ # qseecom_sample_client v smplap64 15 1 Note: Command line arguments do not belong to legacy test         ---------------------------------------------------------------          WARNING!!! You are about to erase the entire RPMB partition.         ----------------------------------------------------------------          Do you want to proceed (y/n)? y RPMB partition erase completedide

     3)重啓機器,檢查機器處於lock狀態和rpmb key已經provision     adb reboot bootloader     執行下面命令查看locked狀態     fastboot oem lock (bootloader)    Device already : locked! OKAY [  0.006s] Finished. Total time: 0.007s測試

         執行下面命令,若返回-1表示已經provision過rpmb key          MODEL1:/ # qseecom_sample_client v smplap64 14 1 Note: Command line arguments do not belong to legacy test         -------------------------------------------------------          WARNING!!! You are about to provision the RPMB key.          This is a ONE time operation and CANNOT be reversed.         -------------------------------------------------------          0 -> Provision Production key          1 -> Provision Test key          2 -> Check RPMB key provision status         -------------------------------------------------------          Select an option to proceed: 1 RPMB key provisioning failed (-1)debug

   4) 後面就能夠進行attestation key provison了     adb push keybox.xml /data/local/tmp     adb shell LD_LIBRARY_PATH=/vendor/lib64/hw KmInstallKeybox /data/local/tmp/keybox.xml your_key_file_product_id true    5)在user版本上測試時注意不要刷persist image,由於attestation key是寫在persist分區的。xml

widevine要用到的話,也得先合入。能夠參考 kba-160918225319_3_how_to_integrate_widevine_on_android.pdf,Integrate Widevine - GMS Help.pdf等文檔。文檔

而後,絕大部分問題都是高通的問題……不少都是閉源的,無能爲力。it

相關文章
相關標籤/搜索