42 lines
1.6 KiB
XML
42 lines
1.6 KiB
XML
<!-- Vendor mapping file -->
|
|
<!-- Sample UUID to list of UIDs mapping file -->
|
|
|
|
<!-- UUID: Universally Unique IDentifier -->
|
|
<!-- 16 Byte UUID need to be generated by vendors to add new entry -->
|
|
<!-- As per global platform access control spec, UUID is expected to be of -->
|
|
<!-- length 20 bytes. While using this UUID, it is expected to be -->
|
|
<!-- automatically padded with ffffffff in initial 4 bytes of 20 Byte length -->
|
|
|
|
<!-- UID: user identifier of the service -->
|
|
|
|
<!-- This mapping file should contain an entry for VTS tests, since VTS -->
|
|
<!-- tests run as root, user identifier 0 should be mapped to its -->
|
|
<!-- corresponding UUID to allow VTS tests to access secure element -->
|
|
<!-- For VTS tests use UID: 0 and UUID: 9f36407ead0639fc966f14dde7970f68 -->
|
|
|
|
<ref_do>
|
|
<!-- mapping entries to map unique identifiers to device hal services -->
|
|
<!-- uids -->
|
|
|
|
<!-- UUID would be automatically padding with ffffffff to fulfill 20 -->
|
|
<!-- bytes in access rule. For example for -->
|
|
<!-- UUID:9f36407ead0639fc966f14dde7970f68 after padding it should look -->
|
|
<!-- like ffffffff9f36407ead0639fc966f14dde7970f68 -->
|
|
<uuid_ref_do>
|
|
<uids>
|
|
<uid>0</uid>
|
|
</uids>
|
|
<uuid>9f36407ead0639fc966f14dde7970f68</uuid>
|
|
</uuid_ref_do>
|
|
|
|
<!-- Sample mapping entry with UIDs:1096 and 1097 mapped to -->
|
|
<!-- UUID:9f36407ead0639fc966f14dde7970f68 -->
|
|
<uuid_ref_do>
|
|
<uids>
|
|
<uid>1096</uid>
|
|
<uid>1097</uid>
|
|
</uids>
|
|
<uuid>a9b7ba70783b317e9998dc4dd82eb3c5</uuid>
|
|
</uuid_ref_do>
|
|
</ref_do>
|