Home | History | Annotate | only in /external/libese/tools/ese_ls_provision
Up to higher level directory
NameDateSize
Android.bp06-Dec-2017984
ese_ls_provision.cpp06-Dec-20175.4K
README.md06-Dec-20171.4K

README.md

      1 # ese-ls-provision tool
      2 
      3 Runs on Android host and uploads scripts to the secure element loader service.
      4 
      5 ## Introduction
      6 
      7 PN80T and later secure elements include a "loader service" which runs signed, encrypted scripts to
      8 perform high-privilege operations like installing and deleting applets in a secure way. The result
      9 of compiling, encrypting and signing these scripts with the `ls-cgt.jar` tool is a file containing
     10 hexadecimal blocks separated by newlines; the first line usually starting with `7f21` indicating
     11 the certificate for the signing key. This tool takes those signed, encrypted scripts and sends
     12 them to the secure element.
     13 
     14 ## Usage
     15 
     16     ese-ls-provision <identifier> <script> <responsefile>
     17 
     18 - `<identifier>` names a file of one to twenty bytes. This is a required parameter to the code
     19 which drives communication with the loader service, and the identifier is sent to the SE as part
     20 of the initial setup, but I'm not sure what effect it has apart from that; the source code says
     21 "It is used to provide the ALA with an Unique Identifier of the Application that has triggered the
     22 ALA script".
     23 - `<script>` is the compiled, encrypted, signed scrypt as generated by `ls-cgt.jar`.
     24 - `<responsefile>` is a file to which to write the response from the loader service. This is also
     25 written as newline-separated hexadecimal. On a successful upload, each line ends with `9000`.
     26 
     27