Lines Matching refs:as

4 It is specified as [a HAL][secretkeeperhal] and must be implemented in an environment with
6 such as ARM TrustZone.
10 clients as well as deletion of some or all data.
18 In the key exchange protocol, the client acts as P1 (source) and Secretkeeper as P2 (sink). The
50 Android provides a reference implementation of Secretkeeper as well as the required AuthGraph Key
65 5. [./dice_policy/][dice_policy_dir]: Contains code for building dice_policies as well
66    as well as matching them against Dice chain. As explained [here](#Policy-Gated-Storage), this
114 Secretkeeper appears as a HAL service in userspace, and so an executable that registers for and
130 one for AuthGraph), as encapsulated in the `authgraph_hal::channel::SerializedChannel` trait.
132 This trait has a single method `execute()`, which takes as input a request message (as bytes), and
133 returns a response message (as bytes) or an error.
136 which allows it to service Binder requests by forwarding the requests to the TA as request/response
181 bootloader is required to retrieve the identity of Secretkeeper (expressed as a public key) at boot
182 time so that the identity can be (securely) provided to pVM instances, as described
242 As described [above](#authgraph-key-exchange), Microdroid as a Secretkeeper
248 pair and use that as its identity in the AuthGraph protocol. The public key from
252 The public key is transported as a CBOR-encoded COSE_key, as a PubKeyEd25519 /
253 PubKeyECDSA256 / PubKeyECDSA384 as defined in
256 Microdroid expects the public key to be present in the Linux device tree as the