1<!-- Vendor mapping file --> 2<!-- Sample UUID to list of UIDs mapping file --> 3 4<!-- UUID: Universally Unique IDentifier --> 5<!-- 16 Byte UUID need to be generated by vendors to add new entry --> 6<!-- As per global platform access control spec, UUID is expected to be of --> 7<!-- length 20 bytes. While using this UUID, it is expected to be --> 8<!-- automatically padded with ffffffff in initial 4 bytes of 20 Byte length --> 9 10<!-- UID: user identifier of the service --> 11 12<!-- This mapping file should contain an entry for VTS tests, since VTS --> 13<!-- tests run as root, user identifier 0 should be mapped to its --> 14<!-- corresponding UUID to allow VTS tests to access secure element --> 15<!-- For VTS tests use UID: 0 and UUID: 9f36407ead0639fc966f14dde7970f68 --> 16 17<ref_do> 18 <!-- mapping entries to map unique identifiers to device hal services --> 19 <!-- uids --> 20 21 <!-- UUID would be automatically padding with ffffffff to fulfill 20 --> 22 <!-- bytes in access rule. For example for --> 23 <!-- UUID:9f36407ead0639fc966f14dde7970f68 after padding it should look --> 24 <!-- like ffffffff9f36407ead0639fc966f14dde7970f68 --> 25 <uuid_ref_do> 26 <uids> 27 <uid>0</uid> 28 </uids> 29 <uuid>9f36407ead0639fc966f14dde7970f68</uuid> 30 </uuid_ref_do> 31 32 <!-- Sample mapping entry with UIDs:1096 and 1097 mapped to --> 33 <!-- UUID:9f36407ead0639fc966f14dde7970f68 --> 34 <uuid_ref_do> 35 <uids> 36 <uid>2901</uid> 37 <uid>2902</uid> 38 </uids> 39 <uuid>636F6D2E6E78702E7365637572697479</uuid> 40 </uuid_ref_do> 41</ref_do> 42