mbedtls/docs
Gilles Peskine 1bc9c4c8c8 Make entry points mandatory in capabilities
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>
2020-08-07 22:47:15 +02:00
..
architecture Merge pull request #3493 from gilles-peskine-arm/psa-unified-driver-specs 2020-08-06 16:10:17 +01:00
proposed Make entry points mandatory in capabilities 2020-08-07 22:47:15 +02:00
.gitignore Add a directory for proposed specifications 2020-07-13 13:27:42 +02:00
getting_started.md Rename ECC Family Macros According to PSA Spec 2020-07-02 16:59:30 +01:00
PSACryptoDriverModelSpec.pdf Add generated documentation for mbedcrypto-0.1.0b 2018-11-26 17:21:23 +00:00