From dff10c773bd4a2bf5c8a94cb596c2ffb6c73ceb5 Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Tue, 24 Mar 2020 22:50:26 +0100 Subject: [PATCH] Add a note that TLS requires further consideration Signed-off-by: Gilles Peskine --- docs/architecture/testing/invasive-testing.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/architecture/testing/invasive-testing.md b/docs/architecture/testing/invasive-testing.md index 10fdb1aee..35d117bc9 100644 --- a/docs/architecture/testing/invasive-testing.md +++ b/docs/architecture/testing/invasive-testing.md @@ -1,13 +1,17 @@ -# Mbed Crypto invasive testing strategy +# Mbed TLS invasive testing strategy ## Introduction -In Mbed Crypto and Mbed TLS, we use black-box testing as much as possible: test the documented behavior of the product, in a realistic environment. However this is not always sufficient. +In Mbed TLS, we use black-box testing as much as possible: test the documented behavior of the product, in a realistic environment. However this is not always sufficient. The goal of this document is to identify areas where black-box testing is insufficient and to propose solutions. This is a test strategy document, not a test plan. A description of exactly what is tested is out of scope. +### TLS + +This document currently focuses on data structure manipulation and storage, which is what the crypto/keystore and X.509 parts of the library are about. More work is needed to fully take TLS into account. + ## Rules Always follow these rules unless you have a good reason not to. If you deviate, document the rationale somewhere.