2018-11-30 17:54:54 +00:00
|
|
|
/*
|
|
|
|
* PSA crypto layer on top of Mbed TLS crypto
|
|
|
|
*/
|
|
|
|
/* Copyright (C) 2018, ARM Limited, All Rights Reserved
|
|
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
|
|
* not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
|
|
* WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*
|
|
|
|
* This file is part of mbed TLS (https://tls.mbed.org)
|
|
|
|
*/
|
|
|
|
|
|
|
|
#if !defined(MBEDTLS_CONFIG_FILE)
|
|
|
|
#include "mbedtls/config.h"
|
|
|
|
#else
|
|
|
|
#include MBEDTLS_CONFIG_FILE
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#if defined(MBEDTLS_PSA_CRYPTO_C)
|
|
|
|
|
2019-02-14 08:28:02 +00:00
|
|
|
#include "psa_crypto_service_integration.h"
|
2018-11-30 17:54:54 +00:00
|
|
|
#include "psa/crypto.h"
|
|
|
|
|
2018-12-10 15:29:04 +00:00
|
|
|
#include "psa_crypto_core.h"
|
2018-11-30 17:54:54 +00:00
|
|
|
#include "psa_crypto_slot_management.h"
|
|
|
|
#include "psa_crypto_storage.h"
|
|
|
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <string.h>
|
|
|
|
#if defined(MBEDTLS_PLATFORM_C)
|
|
|
|
#include "mbedtls/platform.h"
|
|
|
|
#else
|
|
|
|
#define mbedtls_calloc calloc
|
|
|
|
#define mbedtls_free free
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#define ARRAY_LENGTH( array ) ( sizeof( array ) / sizeof( *( array ) ) )
|
|
|
|
|
2018-12-10 15:29:04 +00:00
|
|
|
typedef struct
|
|
|
|
{
|
|
|
|
psa_key_slot_t key_slots[PSA_KEY_SLOT_COUNT];
|
|
|
|
unsigned key_slots_initialized : 1;
|
|
|
|
} psa_global_data_t;
|
|
|
|
|
2018-12-12 13:05:08 +00:00
|
|
|
static psa_global_data_t global_data;
|
2018-12-10 15:29:04 +00:00
|
|
|
|
|
|
|
/* Access a key slot at the given handle. The handle of a key slot is
|
|
|
|
* the index of the slot in the global slot array, plus one so that handles
|
|
|
|
* start at 1 and not 0. */
|
|
|
|
psa_status_t psa_get_key_slot( psa_key_handle_t handle,
|
|
|
|
psa_key_slot_t **p_slot )
|
|
|
|
{
|
|
|
|
psa_key_slot_t *slot = NULL;
|
|
|
|
|
|
|
|
if( ! global_data.key_slots_initialized )
|
|
|
|
return( PSA_ERROR_BAD_STATE );
|
|
|
|
|
|
|
|
/* 0 is not a valid handle under any circumstance. This
|
|
|
|
* implementation provides slots number 1 to N where N is the
|
|
|
|
* number of available slots. */
|
|
|
|
if( handle == 0 || handle > ARRAY_LENGTH( global_data.key_slots ) )
|
|
|
|
return( PSA_ERROR_INVALID_HANDLE );
|
|
|
|
slot = &global_data.key_slots[handle - 1];
|
|
|
|
|
|
|
|
/* If the slot hasn't been allocated, the handle is invalid. */
|
|
|
|
if( ! slot->allocated )
|
|
|
|
return( PSA_ERROR_INVALID_HANDLE );
|
|
|
|
|
|
|
|
*p_slot = slot;
|
|
|
|
return( PSA_SUCCESS );
|
|
|
|
}
|
|
|
|
|
|
|
|
psa_status_t psa_initialize_key_slots( void )
|
|
|
|
{
|
|
|
|
/* Nothing to do: program startup and psa_wipe_all_key_slots() both
|
|
|
|
* guarantee that the key slots are initialized to all-zero, which
|
|
|
|
* means that all the key slots are in a valid, empty state. */
|
|
|
|
global_data.key_slots_initialized = 1;
|
|
|
|
return( PSA_SUCCESS );
|
|
|
|
}
|
|
|
|
|
|
|
|
void psa_wipe_all_key_slots( void )
|
|
|
|
{
|
|
|
|
psa_key_handle_t key;
|
|
|
|
for( key = 1; key <= PSA_KEY_SLOT_COUNT; key++ )
|
|
|
|
{
|
|
|
|
psa_key_slot_t *slot = &global_data.key_slots[key - 1];
|
|
|
|
(void) psa_wipe_key_slot( slot );
|
|
|
|
}
|
|
|
|
global_data.key_slots_initialized = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/** Find a free key slot and mark it as in use.
|
|
|
|
*
|
2018-12-11 14:51:32 +00:00
|
|
|
* \param[out] handle On success, a slot number that is not in use. This
|
|
|
|
* value can be used as a handle to the slot.
|
2018-12-10 15:29:04 +00:00
|
|
|
*
|
|
|
|
* \retval #PSA_SUCCESS
|
|
|
|
* \retval #PSA_ERROR_INSUFFICIENT_MEMORY
|
|
|
|
*/
|
|
|
|
static psa_status_t psa_internal_allocate_key_slot( psa_key_handle_t *handle )
|
|
|
|
{
|
|
|
|
for( *handle = PSA_KEY_SLOT_COUNT; *handle != 0; --( *handle ) )
|
|
|
|
{
|
|
|
|
psa_key_slot_t *slot = &global_data.key_slots[*handle - 1];
|
|
|
|
if( ! slot->allocated )
|
|
|
|
{
|
|
|
|
slot->allocated = 1;
|
|
|
|
return( PSA_SUCCESS );
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return( PSA_ERROR_INSUFFICIENT_MEMORY );
|
|
|
|
}
|
|
|
|
|
2018-12-10 15:48:53 +00:00
|
|
|
/** Wipe a key slot and mark it as available.
|
|
|
|
*
|
|
|
|
* This does not affect persistent storage.
|
|
|
|
*
|
2018-12-11 14:51:32 +00:00
|
|
|
* \param handle The handle to the key slot to release.
|
2018-12-10 15:48:53 +00:00
|
|
|
*
|
|
|
|
* \retval #PSA_SUCCESS
|
|
|
|
* \retval #PSA_ERROR_INVALID_ARGUMENT
|
|
|
|
* \retval #PSA_ERROR_TAMPERING_DETECTED
|
|
|
|
*/
|
|
|
|
static psa_status_t psa_internal_release_key_slot( psa_key_handle_t handle )
|
|
|
|
{
|
|
|
|
psa_key_slot_t *slot;
|
|
|
|
psa_status_t status;
|
|
|
|
|
|
|
|
status = psa_get_key_slot( handle, &slot );
|
|
|
|
if( status != PSA_SUCCESS )
|
|
|
|
return( status );
|
|
|
|
|
|
|
|
return( psa_wipe_key_slot( slot ) );
|
|
|
|
}
|
|
|
|
|
2019-01-19 11:20:52 +00:00
|
|
|
psa_status_t psa_allocate_key( psa_key_handle_t *handle )
|
2018-11-30 17:54:54 +00:00
|
|
|
{
|
|
|
|
*handle = 0;
|
|
|
|
return( psa_internal_allocate_key_slot( handle ) );
|
|
|
|
}
|
|
|
|
|
2018-12-10 15:48:53 +00:00
|
|
|
#if defined(MBEDTLS_PSA_CRYPTO_STORAGE_C)
|
|
|
|
static psa_status_t psa_load_persistent_key_into_slot( psa_key_slot_t *p_slot )
|
|
|
|
{
|
|
|
|
psa_status_t status = PSA_SUCCESS;
|
|
|
|
uint8_t *key_data = NULL;
|
|
|
|
size_t key_data_length = 0;
|
|
|
|
|
|
|
|
status = psa_load_persistent_key( p_slot->persistent_storage_id,
|
|
|
|
&( p_slot )->type,
|
|
|
|
&( p_slot )->policy, &key_data,
|
|
|
|
&key_data_length );
|
|
|
|
if( status != PSA_SUCCESS )
|
|
|
|
goto exit;
|
|
|
|
status = psa_import_key_into_slot( p_slot,
|
|
|
|
key_data, key_data_length );
|
|
|
|
exit:
|
|
|
|
psa_free_persistent_key_data( key_data, key_data_length );
|
|
|
|
return( status );
|
|
|
|
}
|
2019-02-19 12:04:02 +00:00
|
|
|
|
|
|
|
/** Check whether a key identifier is acceptable.
|
|
|
|
*
|
|
|
|
* For backward compatibility, key identifiers that were valid in a
|
|
|
|
* past released version must remain valid, unless a migration path
|
|
|
|
* is provided.
|
|
|
|
*
|
Support encoding an owner in key file IDs
Differentiate between _key identifiers_, which are always `uint32_t`,
and _key file identifiers_, which are platform-dependent. Normally,
the two are the same.
In `psa/crypto_platform.h`, define `psa_app_key_id_t` (which is always
32 bits, the standard key identifier type) and
`psa_key_file_id_t` (which will be different in some service builds).
A subsequent commit will introduce a platform where the two are different.
It would make sense for the function declarations in `psa/crypto.h` to
use `psa_key_file_id_t`. However this file is currently part of the
PSA Crypto API specification, so it must stick to the standard type
`psa_key_id_t`. Hence, as long as the specification and Mbed Crypto
are not separate, use the implementation-specific file
`psa/crypto_platform.h` to define `psa_key_id_t` as `psa_key_file_id_t`.
In the library, systematically use `psa_key_file_id_t`.
perl -i -pe 's/psa_key_id_t/psa_key_file_id_t/g' library/*.[hc]
2019-02-19 12:24:37 +00:00
|
|
|
* \param file_id The key identifier to check.
|
2019-05-06 16:56:30 +00:00
|
|
|
* \param vendor_ok Nonzero to allow key ids in the vendor range.
|
|
|
|
* 0 to allow only key ids in the application range.
|
2019-02-19 12:04:02 +00:00
|
|
|
*
|
Support encoding an owner in key file IDs
Differentiate between _key identifiers_, which are always `uint32_t`,
and _key file identifiers_, which are platform-dependent. Normally,
the two are the same.
In `psa/crypto_platform.h`, define `psa_app_key_id_t` (which is always
32 bits, the standard key identifier type) and
`psa_key_file_id_t` (which will be different in some service builds).
A subsequent commit will introduce a platform where the two are different.
It would make sense for the function declarations in `psa/crypto.h` to
use `psa_key_file_id_t`. However this file is currently part of the
PSA Crypto API specification, so it must stick to the standard type
`psa_key_id_t`. Hence, as long as the specification and Mbed Crypto
are not separate, use the implementation-specific file
`psa/crypto_platform.h` to define `psa_key_id_t` as `psa_key_file_id_t`.
In the library, systematically use `psa_key_file_id_t`.
perl -i -pe 's/psa_key_id_t/psa_key_file_id_t/g' library/*.[hc]
2019-02-19 12:24:37 +00:00
|
|
|
* \return 1 if \p file_id is acceptable, otherwise 0.
|
2019-02-19 12:04:02 +00:00
|
|
|
*/
|
2019-05-06 16:56:30 +00:00
|
|
|
static int psa_is_key_id_valid( psa_key_file_id_t file_id,
|
|
|
|
int vendor_ok )
|
2019-02-19 12:04:02 +00:00
|
|
|
{
|
Support encoding an owner in key file IDs
Differentiate between _key identifiers_, which are always `uint32_t`,
and _key file identifiers_, which are platform-dependent. Normally,
the two are the same.
In `psa/crypto_platform.h`, define `psa_app_key_id_t` (which is always
32 bits, the standard key identifier type) and
`psa_key_file_id_t` (which will be different in some service builds).
A subsequent commit will introduce a platform where the two are different.
It would make sense for the function declarations in `psa/crypto.h` to
use `psa_key_file_id_t`. However this file is currently part of the
PSA Crypto API specification, so it must stick to the standard type
`psa_key_id_t`. Hence, as long as the specification and Mbed Crypto
are not separate, use the implementation-specific file
`psa/crypto_platform.h` to define `psa_key_id_t` as `psa_key_file_id_t`.
In the library, systematically use `psa_key_file_id_t`.
perl -i -pe 's/psa_key_id_t/psa_key_file_id_t/g' library/*.[hc]
2019-02-19 12:24:37 +00:00
|
|
|
psa_app_key_id_t key_id = PSA_KEY_FILE_GET_KEY_ID( file_id );
|
2019-05-15 16:42:09 +00:00
|
|
|
if( PSA_KEY_ID_USER_MIN <= key_id && key_id <= PSA_KEY_ID_USER_MAX )
|
|
|
|
return( 1 );
|
|
|
|
else if( vendor_ok &&
|
|
|
|
PSA_KEY_ID_VENDOR_MIN <= key_id &&
|
|
|
|
key_id <= PSA_KEY_ID_VENDOR_MAX )
|
|
|
|
return( 1 );
|
|
|
|
else
|
2019-02-19 12:04:02 +00:00
|
|
|
return( 0 );
|
|
|
|
}
|
2018-12-10 15:48:53 +00:00
|
|
|
|
|
|
|
/** Declare a slot as persistent and load it from storage.
|
|
|
|
*
|
|
|
|
* This function may only be called immediately after a successful call
|
|
|
|
* to psa_internal_allocate_key_slot().
|
|
|
|
*
|
|
|
|
* \param handle A handle to a key slot freshly allocated with
|
|
|
|
* psa_internal_allocate_key_slot().
|
|
|
|
*
|
|
|
|
* \retval #PSA_SUCCESS
|
|
|
|
* The slot content was loaded successfully.
|
2019-02-14 11:48:10 +00:00
|
|
|
* \retval #PSA_ERROR_DOES_NOT_EXIST
|
2018-12-10 15:48:53 +00:00
|
|
|
* There is no content for this slot in persistent storage.
|
|
|
|
* \retval #PSA_ERROR_INVALID_HANDLE
|
|
|
|
* \retval #PSA_ERROR_INVALID_ARGUMENT
|
|
|
|
* \p id is not acceptable.
|
|
|
|
* \retval #PSA_ERROR_INSUFFICIENT_MEMORY
|
|
|
|
* \retval #PSA_ERROR_STORAGE_FAILURE
|
|
|
|
*/
|
|
|
|
static psa_status_t psa_internal_make_key_persistent( psa_key_handle_t handle,
|
Support encoding an owner in key file IDs
Differentiate between _key identifiers_, which are always `uint32_t`,
and _key file identifiers_, which are platform-dependent. Normally,
the two are the same.
In `psa/crypto_platform.h`, define `psa_app_key_id_t` (which is always
32 bits, the standard key identifier type) and
`psa_key_file_id_t` (which will be different in some service builds).
A subsequent commit will introduce a platform where the two are different.
It would make sense for the function declarations in `psa/crypto.h` to
use `psa_key_file_id_t`. However this file is currently part of the
PSA Crypto API specification, so it must stick to the standard type
`psa_key_id_t`. Hence, as long as the specification and Mbed Crypto
are not separate, use the implementation-specific file
`psa/crypto_platform.h` to define `psa_key_id_t` as `psa_key_file_id_t`.
In the library, systematically use `psa_key_file_id_t`.
perl -i -pe 's/psa_key_id_t/psa_key_file_id_t/g' library/*.[hc]
2019-02-19 12:24:37 +00:00
|
|
|
psa_key_file_id_t id )
|
2018-12-10 15:48:53 +00:00
|
|
|
{
|
|
|
|
psa_key_slot_t *slot;
|
|
|
|
psa_status_t status;
|
|
|
|
|
|
|
|
status = psa_get_key_slot( handle, &slot );
|
|
|
|
if( status != PSA_SUCCESS )
|
|
|
|
return( status );
|
|
|
|
|
|
|
|
slot->lifetime = PSA_KEY_LIFETIME_PERSISTENT;
|
|
|
|
slot->persistent_storage_id = id;
|
|
|
|
status = psa_load_persistent_key_into_slot( slot );
|
|
|
|
|
|
|
|
return( status );
|
|
|
|
}
|
2019-04-25 11:47:40 +00:00
|
|
|
#endif /* defined(MBEDTLS_PSA_CRYPTO_STORAGE_C) */
|
2018-12-10 15:48:53 +00:00
|
|
|
|
2019-04-19 16:19:40 +00:00
|
|
|
psa_status_t psa_validate_persistent_key_parameters(
|
|
|
|
psa_key_lifetime_t lifetime,
|
2019-05-06 16:56:30 +00:00
|
|
|
psa_key_file_id_t id,
|
|
|
|
int creating )
|
2019-04-19 16:19:40 +00:00
|
|
|
{
|
|
|
|
if( lifetime != PSA_KEY_LIFETIME_PERSISTENT )
|
|
|
|
return( PSA_ERROR_INVALID_ARGUMENT );
|
2019-04-25 11:47:40 +00:00
|
|
|
|
|
|
|
#if defined(MBEDTLS_PSA_CRYPTO_STORAGE_C)
|
2019-05-06 16:56:30 +00:00
|
|
|
if( ! psa_is_key_id_valid( id, ! creating ) )
|
2019-04-19 16:19:40 +00:00
|
|
|
return( PSA_ERROR_INVALID_ARGUMENT );
|
|
|
|
return( PSA_SUCCESS );
|
2019-04-25 11:47:40 +00:00
|
|
|
|
|
|
|
#else /* MBEDTLS_PSA_CRYPTO_STORAGE_C */
|
|
|
|
(void) id;
|
2019-05-15 22:31:48 +00:00
|
|
|
(void) creating;
|
2019-04-25 11:47:40 +00:00
|
|
|
return( PSA_ERROR_NOT_SUPPORTED );
|
|
|
|
#endif /* !MBEDTLS_PSA_CRYPTO_STORAGE_C */
|
2019-04-19 16:19:40 +00:00
|
|
|
}
|
|
|
|
|
2018-11-30 17:54:54 +00:00
|
|
|
static psa_status_t persistent_key_setup( psa_key_lifetime_t lifetime,
|
Support encoding an owner in key file IDs
Differentiate between _key identifiers_, which are always `uint32_t`,
and _key file identifiers_, which are platform-dependent. Normally,
the two are the same.
In `psa/crypto_platform.h`, define `psa_app_key_id_t` (which is always
32 bits, the standard key identifier type) and
`psa_key_file_id_t` (which will be different in some service builds).
A subsequent commit will introduce a platform where the two are different.
It would make sense for the function declarations in `psa/crypto.h` to
use `psa_key_file_id_t`. However this file is currently part of the
PSA Crypto API specification, so it must stick to the standard type
`psa_key_id_t`. Hence, as long as the specification and Mbed Crypto
are not separate, use the implementation-specific file
`psa/crypto_platform.h` to define `psa_key_id_t` as `psa_key_file_id_t`.
In the library, systematically use `psa_key_file_id_t`.
perl -i -pe 's/psa_key_id_t/psa_key_file_id_t/g' library/*.[hc]
2019-02-19 12:24:37 +00:00
|
|
|
psa_key_file_id_t id,
|
2018-11-30 17:54:54 +00:00
|
|
|
psa_key_handle_t *handle,
|
2019-05-06 16:56:30 +00:00
|
|
|
int creating )
|
2018-11-30 17:54:54 +00:00
|
|
|
{
|
|
|
|
psa_status_t status;
|
2019-05-06 16:56:30 +00:00
|
|
|
psa_status_t wanted_load_status =
|
|
|
|
( creating ? PSA_ERROR_DOES_NOT_EXIST : PSA_SUCCESS );
|
2018-11-30 17:54:54 +00:00
|
|
|
|
|
|
|
*handle = 0;
|
|
|
|
|
2019-05-06 16:56:30 +00:00
|
|
|
status = psa_validate_persistent_key_parameters( lifetime, id, creating );
|
2019-04-19 16:19:40 +00:00
|
|
|
if( status != PSA_SUCCESS )
|
|
|
|
return( status );
|
2018-11-30 17:54:54 +00:00
|
|
|
|
2019-04-25 11:47:40 +00:00
|
|
|
#if defined(MBEDTLS_PSA_CRYPTO_STORAGE_C)
|
2018-11-30 17:54:54 +00:00
|
|
|
status = psa_internal_allocate_key_slot( handle );
|
|
|
|
if( status != PSA_SUCCESS )
|
|
|
|
return( status );
|
|
|
|
|
|
|
|
status = psa_internal_make_key_persistent( *handle, id );
|
|
|
|
if( status != wanted_load_status )
|
|
|
|
{
|
|
|
|
psa_internal_release_key_slot( *handle );
|
|
|
|
*handle = 0;
|
|
|
|
}
|
|
|
|
return( status );
|
2019-04-25 11:47:40 +00:00
|
|
|
#else /* defined(MBEDTLS_PSA_CRYPTO_STORAGE_C) */
|
|
|
|
(void) wanted_load_status;
|
|
|
|
return( PSA_ERROR_NOT_SUPPORTED );
|
|
|
|
#endif /* !defined(MBEDTLS_PSA_CRYPTO_STORAGE_C) */
|
2018-11-30 17:54:54 +00:00
|
|
|
}
|
|
|
|
|
2019-05-06 16:44:55 +00:00
|
|
|
psa_status_t psa_open_key( psa_key_file_id_t id, psa_key_handle_t *handle )
|
2018-11-30 17:54:54 +00:00
|
|
|
{
|
2019-05-06 16:44:55 +00:00
|
|
|
return( persistent_key_setup( PSA_KEY_LIFETIME_PERSISTENT,
|
2019-05-06 16:56:30 +00:00
|
|
|
id, handle, 0 ) );
|
2018-11-30 17:54:54 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
psa_status_t psa_create_key( psa_key_lifetime_t lifetime,
|
Support encoding an owner in key file IDs
Differentiate between _key identifiers_, which are always `uint32_t`,
and _key file identifiers_, which are platform-dependent. Normally,
the two are the same.
In `psa/crypto_platform.h`, define `psa_app_key_id_t` (which is always
32 bits, the standard key identifier type) and
`psa_key_file_id_t` (which will be different in some service builds).
A subsequent commit will introduce a platform where the two are different.
It would make sense for the function declarations in `psa/crypto.h` to
use `psa_key_file_id_t`. However this file is currently part of the
PSA Crypto API specification, so it must stick to the standard type
`psa_key_id_t`. Hence, as long as the specification and Mbed Crypto
are not separate, use the implementation-specific file
`psa/crypto_platform.h` to define `psa_key_id_t` as `psa_key_file_id_t`.
In the library, systematically use `psa_key_file_id_t`.
perl -i -pe 's/psa_key_id_t/psa_key_file_id_t/g' library/*.[hc]
2019-02-19 12:24:37 +00:00
|
|
|
psa_key_file_id_t id,
|
2018-11-30 17:54:54 +00:00
|
|
|
psa_key_handle_t *handle )
|
|
|
|
{
|
|
|
|
psa_status_t status;
|
|
|
|
|
2019-05-06 16:56:30 +00:00
|
|
|
status = persistent_key_setup( lifetime, id, handle, 1 );
|
2018-11-30 17:54:54 +00:00
|
|
|
switch( status )
|
|
|
|
{
|
2019-02-14 11:48:10 +00:00
|
|
|
case PSA_SUCCESS: return( PSA_ERROR_ALREADY_EXISTS );
|
|
|
|
case PSA_ERROR_DOES_NOT_EXIST: return( PSA_SUCCESS );
|
2018-11-30 17:54:54 +00:00
|
|
|
default: return( status );
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
psa_status_t psa_close_key( psa_key_handle_t handle )
|
|
|
|
{
|
|
|
|
return( psa_internal_release_key_slot( handle ) );
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif /* MBEDTLS_PSA_CRYPTO_C */
|