2019-10-10 20:30:54 +02:00
|
|
|
/**
|
|
|
|
|
* \file config-symmetric-only.h
|
|
|
|
|
*
|
|
|
|
|
* \brief Configuration without any asymmetric cryptography.
|
|
|
|
|
*/
|
|
|
|
|
/*
|
2020-08-07 13:07:28 +02:00
|
|
|
* Copyright The Mbed TLS Contributors
|
2023-11-02 19:47:20 +00:00
|
|
|
* SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
|
2019-10-10 20:30:54 +02:00
|
|
|
*/
|
|
|
|
|
|
2021-09-28 21:06:08 +02:00
|
|
|
/* Mbed TLS feature support */
|
2019-10-10 20:30:54 +02:00
|
|
|
#define MBEDTLS_ERROR_STRERROR_DUMMY
|
|
|
|
|
#define MBEDTLS_VERSION_FEATURES
|
|
|
|
|
|
Have MBEDTLS_TIMING_C require MBEDTLS_HAVE_TIME
Nowadays, the timing module just builds on a function that provides a timer
with millisecond resolution. In terms of platform requirements, this is
almost exactly equivalent to `mbedtls_ms_time()`
provides (`mbedtls_ms_time()` is arguably a little stronger because it is
supposed to last longer than a single timer object, but an application could
start a timer when it starts, so there's no real difference.) So it's a bit
silly that `timing.c` essentially reimplements this. Rely on
`mbedtls_ms_time()` instead.
This is an API break because in Mbed TLS 4.0, it was possible to enable
`MBEDTLS_TIMING_C` without `MBEDTLS_HAVE_TIME`. However, `timing.c` only
provided an implementation for Windows and Unix-like platforms, and on those
platforms, it is very likely that the default implementation of
`MBEDTLS_HAVE_TIME` would also work. (The main exception would be a platform
that has the traditional Unix function `gettimeofday()`, but not the 1990s
novelty `clock_gettime()`.) So make this an official requirement, as a
belated change that really should have gone into 4.0 if we'd taken the time
to dig into it.
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2026-02-19 16:26:18 +01:00
|
|
|
#define MBEDTLS_TIMING_C //Only for benchmarking
|
2019-10-10 20:30:54 +02:00
|
|
|
#define MBEDTLS_VERSION_C
|