| commit | 0f833bbbf6fc300d95242fdd6e977e089b2e32e2 | [log] [tgz] |
|---|---|---|
| author | Will Drewry <drewry@google.com> | Fri Mar 10 21:49:53 2017 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Mar 10 21:49:53 2017 +0000 |
| tree | 7aa45326e00665faeb1711832c3989723eaa1359 | |
| parent | 17b30cc3f6999a90534f8f4bf14768f9faeedf1a [diff] | |
| parent | 4aa454a96f80ba674e3f887bc07520b5f5cfebe2 [diff] |
Revert "Clean up and refactor; new hw support" am: 4aa454a96f Change-Id: I0c8f0295b88a90926aeee43dd75ff8060fc7368f
Document last updated: 13 Jan 2017
libese provides a minimal transport wrapper for communicating with embedded secure elements. Embedded secure elements typically adhere to smart card standards whose translation is not always smooth when migrated to an always connected bus, like SPI. The interfaces exposed by libese should enable higher level "terminal" implementations to be written on top and/or a service which provides a similar interface.
Behind the interface, libese should help smooth over the differences between eSEs and smart cards use in the hardware adapter implementations. Additionally, a T=1 implementation is supplied, as it appears to be the most common wire transport for these chips.
(TBD: See tools/ and example/)
At present, only sample backends and a Linux SPIdev driven NXP developer board are supported.