Owner: mnissler Bug: http://b/25969241, http://b/27101983

Clone this repo:
  1. 749b023 Migrate Test Targets to New Android Ownership Model am: c88ae5ebd9 by Aditya Choudhary · 10 weeks ago main master
  2. c88ae5e Migrate Test Targets to New Android Ownership Model by Aditya Choudhary · 3 months ago
  3. 61a2022 Add seccomp policy for riscv64 am: 2a488320af am: f9b5669b50 am: 41342ff74e by Chen Guoyin · 1 year, 6 months ago android14-dev android14-mainline-healthfitness-release android14-qpr1-release android14-qpr1-s2-release android14-qpr2-release android14-qpr2-s1-release android14-qpr2-s2-release android14-qpr2-s3-release aml_cfg_341510000 aml_hef_341114030 aml_hef_341311010 aml_hef_341415040 aml_hef_341512030 aml_rkp_341012000 aml_rkp_341015010 aml_rkp_341114000 aml_rkp_341311000 aml_rkp_341510000 android-14.0.0_r16 android-14.0.0_r17 android-14.0.0_r18 android-14.0.0_r19 android-14.0.0_r20 android-14.0.0_r21 android-14.0.0_r22 android-14.0.0_r23 android-14.0.0_r24 android-14.0.0_r25 android-14.0.0_r26 android-14.0.0_r27 android-14.0.0_r29 android-14.0.0_r30 android-14.0.0_r31 android-14.0.0_r32 android-14.0.0_r33
  4. 41342ff Add seccomp policy for riscv64 am: 2a488320af am: f9b5669b50 by Chen Guoyin · 1 year, 6 months ago android-u-beta-1-gpl
  5. f9b5669 Add seccomp policy for riscv64 am: 2a488320af by Chen Guoyin · 1 year, 6 months ago main-16k-with-phones

Access-controlled NVRAM implementation

This repository contains various pieces related to the Access-controlled NVRAM HAL. In a nutshell, the Access-controlled NVRAM HAL allows creation of NVRAM spaces that can hold arbitrary data blobs of limited size. Access restrictions can be configured on each NVRAM space to prevent the contents from being accessed or modified, up to the point of requiring full hardware reset to clear a locked NVRAM space. This can be used for various security features that require a trusted storage location for critical data that an attacker can't tamper with. For details of the NVRAM HAL API, see hardware/libhardware/include/hardware/nvram.h.

client

Contains a simple command-line application to interact with the NVRAM HAL implementation. This is useful for experimentation and use in scripts. nvram-client receives commands and parameters on the command line and translates them to NVRAM HAL calls. Results are printed on stdout.

core

A reference implementation of the NVRAM functionality. This reference implementation can be used to create NVRAM HAL implementations that run in a trusted execution environment. It is also the basis for the testing NVRAM HAL module, which implements the entire NVRAM HAL API surface in userspace for the sake of illustration (but obviously doesn't meet the persistence and tamper-evidence requirements).

Note that the reference implementation leaves persistent storage to be handled by the embedding code, which needs to provide an implementation of the storage interface defined in system/nvram/core/include/nvram/core/storage.h.

hal

The hal directory contains glue code that simplifies creation of NVRAM HAL modules. The code implements the API surface specified by the nvram.h HAL header and translates calls into the request/response message format defined in the messages directory. Thus, to create a working NVRAM HAL module, it is sufficient to provide an implementation that understands nvram::Request and nvram::Response objects, the glue code will adapt it to the full NVRAM API surface.

messages

Defines an IPC message format that can be used to serialize NVRAM HAL calls and their parameters in preparation for sending them elsewhere (e.g., a TEE) for execution. There is a request and a response struct corresponding to each NVRAM HAL function. The nvram::Request and nvram::Response wrappers keep track of the actual request or response type, respectively, as well as the request or response parameters specific to the type.