| commit | 10f57a50a064623372af4b599f4fe8003e771205 | [log] [tgz] |
|---|---|---|
| author | Bill Richardson <wfrichar@google.com> | Mon Jun 04 14:45:09 2018 -0700 |
| committer | Bill Richardson <wfrichar@google.com> | Mon Jun 04 14:46:05 2018 -0700 |
| tree | db2396a8599cc424953b9d503cfeb1bde3b6d761 | |
| parent | 77ec341ff657ce28ea9b88d76966ce10c7836ad6 [diff] |
NUGGET_PARAM_ENABLE_UPDATE tells us whether it worked or not Giving the wrong password still fails, but now with the correct password this call now returns a boolean indicating whether the header was CHANGED to valid. If it was, the AP should request or force a Citadel reboot to give the new image a chance to run. If nothing changed, there's no need to do that. Bug: b/72983372 Test: Manual update, entered PIN, repeat Change-Id: I763d9519c4f5cfa93ac513f13baf5d53f0b3bae6 Signed-off-by: Bill Richardson <wfrichar@google.com>
Android communicates with Nugget apps in order to implement security related HALs. Currently, those HALs are Keymaster, Weaver and OemLock.
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.
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:
NuggetClient on top of call_application()citadelThis directory contains the components to support Citadel connected to Android.