commit | f29bb53671e5aa9f88f84cd38dc1d2fd6e390c80 | [log] [tgz] |
---|---|---|
author | nagendra modadugu <ngm@google.com> | Tue Feb 05 21:37:05 2019 -0800 |
committer | nagendra modadugu <ngm@google.com> | Mon Mar 25 21:49:31 2019 -0700 |
tree | 867661c91afec9f6fd55ef576e383a81c61f8b4c | |
parent | f12b8952b392b241774d0c72c39f32d8682460e6 [diff] |
keymaster: consume all data passed to finish() In the previous implementation, it was possible for excess data to remain unprocessed once the finish() call had completed. This issue went unnoticed until a recent VTS change. Bug: 120993832 Bug: 119749175 Test: VTS passes Change-Id: Id01710e4ed01e5899dff35e0fa6100882906b336 Signed-off-by: nagendra modadugu <ngm@google.com> (cherry picked from commit f0afd5b56f5dd918a05b80d86d2b772048868816)
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()
citadel
This directory contains the components to support Citadel connected to Android.