Revert "keymaster: include date in os_patchlevel"

Turns out that the bug was in nugget, with firmware
using SYSTEM_PATCH_LEVEL in place of BOOT_PATCH_LEVEL.

This reverts commit 5eb6baddb394ae11a5947867058be2923497babd.
The original commit message is below.

  keymaster: include date in os_patchlevel

  The date field was mysteriously missing
  from the originally patchset.  Further
  attendance has addressed the issue.

Bug: 119549128
Test: attest cert format is as expected & VTS pass
Change-Id: I99da4db36489d356c897c3d77223b9bf174dee29
Signed-off-by: nagendra modadugu <ngm@google.com>
(cherry picked from commit 7b1e22985ded6a0767fed36d884dd350f11e8b91)
1 file changed
tree: 867661c91afec9f6fd55ef576e383a81c61f8b4c
  1. citadel/
  2. hals/
  3. manual_tests/
  4. .checkpatch.conf
  5. .clang-format
  6. Android.bp
  7. LICENSE
  8. METADATA
  9. MODULE_LICENSE_APACHE2
  10. NOTICE
  11. README.md
README.md

Android components for Nugget

Android communicates with Nugget apps in order to implement security related HALs. Currently, those HALs are Keymaster, Weaver and OemLock.

Services

Apps that define a protobuf service will have an app interface class autogenerated. These classes will wrap a NuggetClient. The generator can be found in the generator directory.

Asynchronous communication

Work in progress.

Currently, everything is synchronous and just exposes the call_application() function from the Nugget transport API. In future, asynchronous calls may be desired. Support for this could be added in:

  • Nugget transport API
  • NuggetClient on top of call_application()
  • Generated services

citadel

This directory contains the components to support Citadel connected to Android.