Gilles Peskine 1a2904c49a derive_input test function: Try output afterwards ... After passing some inputs, try getting one byte of output, just to check that this succeeds (for a valid sequence of inputs) or fails with BAD_STATE (for an invalid sequence of inputs). Either output a 1-byte key or a 1-byte buffer depending on the test data. The test data was expanded as follows: * Output key type (or not a key): same as the SECRET input if success is expected, otherwise NONE. * Expected status: PSA_SUCCESS after valid inputs, BAD_STATE after any invalid input.		2019-09-24 18:39:03 +02:00
..
.jenkins	Add a Jenkinsfile for PR job testing	2018-10-19 16:41:54 +01:00
data_files	Merge 'mbedtls/development' into merge-crypto-development-20190806	2019-08-06 19:09:55 +02:00
docker/bionic	Improve compatibility with firewalled networks	2019-06-29 17:45:34 -05:00
git-scripts	Merge development commit 8e76332 into development-psa	2019-01-31 08:20:20 -05:00
scripts	Merge pull request #115 from gilles-peskine-arm/psa-error-compatibility_aliases	2019-09-19 16:20:08 +02:00
suites	derive_input test function: Try output afterwards	2019-09-24 18:39:03 +02:00
.gitignore	PSA return status coverage script	2019-09-06 19:28:47 +02:00
CMakeLists.txt	crypto_se_driver: add mock tests	2019-08-21 16:56:16 +01:00
Descriptions.txt	Remove tests that depend on TLS or X.509	2019-03-11 16:49:26 +00:00
make-in-docker.sh	Clean up file prologue comments	2019-06-29 17:45:34 -05:00
Makefile	PSA return status coverage script	2019-09-06 19:28:47 +02:00
psa_crypto_helpers.h	PSA return status coverage script	2019-09-06 19:28:47 +02:00
psa_helpers.h	Move the one non-crypto-specific PSA helper macro to a new header	2019-06-20 12:54:43 +02:00