pioduino/esp-idf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Provide translation for ecdsa.rst and qemu.rst

Browse Source
This commit is contained in:
shenmengjing
2024-03-29 11:25:37 +08:00
committed by BOT
parent 10c22e84ed
commit 4e0c5d3e8e
10 changed files with 228 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/api-reference/peripherals/ecdsa.rst
+3 -1
View File
@@ -1,6 +1,8 @@
Elliptic Curve Digital Signature Algorithm (ECDSA)
==================================================
:link_to_translation:`zh_CN:[中文]`
The Elliptic Curve Digital Signature Algorithm (ECDSA) offers a variant of the Digital Signature Algorithm (DSA) which uses elliptic-curve cryptography.
{IDF_TARGET_NAME}'s ECDSA peripheral provides a secure and efficient environment for computing ECDSA signatures. It offers fast computations while ensuring the confidentiality of the signing process to prevent information leakage. ECDSA private key used in the signing process is accessible only to the hardware peripheral, and it is not readable by software.
@@ -82,7 +84,7 @@ Application Outline
Please refer to the :ref:`ecdsa-peri-with-esp-tls` guide for details on how-to use ECDSA peripheral for establishing a mutually authenticated TLS connection.
The ECDSA peripheral in mbedTLS stack is integrated by overriding the ECDSA sign and verify APIs. Please note that, the ECDSA peripheral does not support all curves or hash algorithms and hence for cases where the requirements do not meet the hardware, implementation falls back to the software.
The ECDSA peripheral in Mbed TLS stack is integrated by overriding the ECDSA signing and verifying APIs. Please note that, the ECDSA peripheral does not support all curves or hash algorithms, and hence for cases where the hardware requirements are not met, the implementation falls back to the software.
For a particular TLS context, additional APIs have been supplied to populate certain fields (e.g., private key ctx) to differentiate routing to hardware. ESP-TLS layer integrates these APIs internally and hence no additional work is required at the application layer. However, for custom use-cases please refer to API details below.
docs/en/api-reference/peripherals/parlio.rst
+2
View File
@@ -1,6 +1,8 @@
Parallel IO
===========
:link_to_translation:`zh_CN:[中文]`
Introduction
------------