mirror of
https://github.com/yuzu-emu/mbedtls.git
synced 2024-11-26 03:35:49 +01:00
Add a note that TLS requires further consideration
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
parent
ab4b9b4165
commit
dff10c773b
@ -1,13 +1,17 @@
|
|||||||
# Mbed Crypto invasive testing strategy
|
# Mbed TLS invasive testing strategy
|
||||||
|
|
||||||
## Introduction
|
## 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.
|
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.
|
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
|
## Rules
|
||||||
|
|
||||||
Always follow these rules unless you have a good reason not to. If you deviate, document the rationale somewhere.
|
Always follow these rules unless you have a good reason not to. If you deviate, document the rationale somewhere.
|
||||||
|
Loading…
Reference in New Issue
Block a user