1bc9c4c8c8
Inferring entry points from algorithms is nice in that it makes capability specifications shorter and less redundant, but that's not really important. It also makes capabilities more fragile: if the core starts supporting new mechanisms based on the same algorithm (for example, adding hash-and-sign when only sign-the-hash existed before), a driver only supporting the old mechanisms would fail at build time. So make entry points mandatory. This has the benefit of making the semantics of capabilities easier to describe. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> |
||
|---|---|---|
| .. | ||
| Makefile | ||
| psa-driver-developer-guide.md | ||
| psa-driver-integration-guide.md | ||
| psa-driver-interface.md | ||
| README | ||
The documents in this directory are proposed specifications for Mbed TLS features. They are not implemented yet, or only partially implemented. Please follow activity on the `development` branch of Mbed TLS if you are interested in these features.