| /mbedtls-latest/library/ |
| D | ssl_cache.c | 81 mbedtls_ssl_cache_entry *entry; in mbedtls_ssl_cache_get() local
89 ret = ssl_cache_find_entry(cache, session_id, session_id_len, &entry); in mbedtls_ssl_cache_get()
95 entry->session, in mbedtls_ssl_cache_get()
96 entry->session_len); in mbedtls_ssl_cache_get()
114 static void ssl_cache_entry_zeroize(mbedtls_ssl_cache_entry *entry) in ssl_cache_entry_zeroize() argument
116 if (entry == NULL) { in ssl_cache_entry_zeroize()
121 if (entry->session != NULL) { in ssl_cache_entry_zeroize()
122 mbedtls_zeroize_and_free(entry->session, entry->session_len); in ssl_cache_entry_zeroize()
126 mbedtls_platform_zeroize(entry, sizeof(mbedtls_ssl_cache_entry)); in ssl_cache_entry_zeroize()
327 mbedtls_ssl_cache_entry *entry; in mbedtls_ssl_cache_remove() local
[all …]
|
| D | x509_crl.c | 217 mbedtls_x509_crl_entry *entry) in x509_get_entries() argument
221 mbedtls_x509_crl_entry *cur_entry = entry; in x509_get_entries()
444 if ((ret = x509_get_entries(&p, end, &crl->entry)) != 0) { in mbedtls_x509_crl_parse_der()
600 const mbedtls_x509_crl_entry *entry; in mbedtls_x509_crl_info() local
628 entry = &crl->entry; in mbedtls_x509_crl_info()
634 while (entry != NULL && entry->raw.len != 0) { in mbedtls_x509_crl_info()
639 ret = mbedtls_x509_serial_gets(p, n, &entry->serial); in mbedtls_x509_crl_info()
644 entry->revocation_date.year, entry->revocation_date.mon, in mbedtls_x509_crl_info()
645 entry->revocation_date.day, entry->revocation_date.hour, in mbedtls_x509_crl_info()
646 entry->revocation_date.min, entry->revocation_date.sec); in mbedtls_x509_crl_info()
[all …]
|
| D | md.c | 884 const md_name_entry *entry = md_names; in mbedtls_md_info_from_string() local
885 while (entry->md_name != NULL && in mbedtls_md_info_from_string()
886 strcmp(entry->md_name, md_name) != 0) { in mbedtls_md_info_from_string()
887 ++entry; in mbedtls_md_info_from_string()
890 return mbedtls_md_info_from_type(entry->md_type); in mbedtls_md_info_from_string()
899 const md_name_entry *entry = md_names; in mbedtls_md_get_name() local
900 while (entry->md_type != MBEDTLS_MD_NONE && in mbedtls_md_get_name()
901 entry->md_type != md_info->type) { in mbedtls_md_get_name()
902 ++entry; in mbedtls_md_get_name()
905 return entry->md_name; in mbedtls_md_get_name()
|
| D | x509_crt.c | 1597 struct dirent *entry; in mbedtls_x509_crt_parse_path() local
1614 while ((entry = readdir(dir)) != NULL) { in mbedtls_x509_crt_parse_path()
1616 "%s/%s", path, entry->d_name); in mbedtls_x509_crt_parse_path()
1992 const mbedtls_x509_crl_entry *cur = &crl->entry; in mbedtls_x509_crt_is_revoked()
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-interface.md | 57 * An object file compiled for the target platform defining the entry point functions specified by t…
79 … and constants referenced by the driver description. They may declare the entry point functions, b…
94 …entry point](#driver-entry-points) or driver entry point family. An entry point is a function defi…
98 …entry point names described by the `"entry_points"` property, to the name of the C function in the…
103 …chanism, it invokes available driver entry points as described in the section [“Driver entry point…
105 A driver is considered available for a cryptographic mechanism that invokes a given entry point if …
107 …`"entry_points"` list either includes the entry point or includes an entry point family that inclu…
121 …entry point, algorithm, key type and key size, and all the capabilities map the entry point to the…
123 If multiple transparent drivers have applicable capabilities for a given combination of entry point…
177 ### Driver entry points
[all …]
|
| D | psa-driver-developer-guide.md | 38 …LS calls driver entry points [as specified in the PSA Cryptography Driver Interface specification]…
|
| D | psa-conditional-inclusion-c.md | 183 #### Conditional inclusion of library entry points
185 An entry point can be eliminated entirely if no algorithm requires it.
205 … key types that apply to that algorithm, no size restriction, and all the entry points that apply …
|
| /mbedtls-latest/docs/ |
| D | psa-driver-example-and-guide.md | 5 …ith Mbed TLS in the future, as well as driver types, operation types, and entry points. As many ke…
10 [Process for Entry Points where auto-generation is implemented](#process-for-entry-points-where-aut…
11 [Process for Entry Points where auto-generation is not implemented](#process-for-entry-points-where…
16 …Operations*. Single-part operations implemented by a driver will have one entry point, while multi…
22 … When a compatible driver is present, the driver wrapper calls the driver entry point function pro…
25 …l have to manually edit the driver dispatch layer and call their driver's entry point functions fr…
27 …he operation entry points specified in the table below. Certain operations are only permitted for …
39 If the driver is accelerating operations whose entry points are in the above table, the instruction…
46 The Mbed TLS driver tests for the aforementioned entry points provide examples of how these deliver…
50 If the driver is accelerating operations whose entry points are not present in the table, a differe…
[all …]
|
| /mbedtls-latest/ChangeLog.d/ |
| D | 00README.md | 1 # Pending changelog entry directory
6 ## What requires a changelog entry?
8 Write a changelog entry if there is a user-visible change. This includes:
30 changelog entry, but not for deciding whether to write one.
32 ## Changelog entry file format
34 A changelog entry file must have the extension `*.txt` and must have the
49 The permitted changelog entry categories are as follows:
64 ## How to write a changelog entry
66 Each entry starts with three spaces, an asterisk and a space. Continuation
|
| /mbedtls-latest/docs/architecture/ |
| D | psa-storage-resilience.md | 73 1. The core calls the driver's `"allocate_key"` entry point.
76 4. The core calls the driver's key creation entry point, passing it the driver's chosen identifier …
89 2. The core calls the driver's `"destroy_key"` entry point.
133 …s information will be stored in a persistent “transaction list”, with one entry per key. In this s…
137 … element). It may call the secure element driver's `"get_key_attributes"` entry point to find out …
156 …entry point. Recovery means resuming the operation where it left off. For key creation, this means…
158 … This requires the secure element driver to have a `"get_key_attributes"` entry point. Compared to…
161 …entry point is potentially problematic because some secure elements don't have room to store key a…
165 Each entry in the transaction list contains the API key identifier, the key lifetime (or at least t…
167 …ion that will go in the key file before calling the driver's key creation entry point. Therefore t…
[all …]
|
| D | psa-crypto-implementation-structure.md | 56 …enerated file corresponding to a pure software implementation. The driver entry points and their c…
73 …entry point as defined in the PSA driver interface specification are named as mbedtls_psa_<driver …
90 * [ ] `ChangeLog.d/*.txt` — changelog entry
141 1. API function defined in `library/psa_crypto.c`. The entry point performs generic checks that don…
|
| D | psa-keystore-design.md | 20 ### Key slot entry points
196 …key-store), a non-empty slot can contain either a volatile key or a cache entry for a persistent o…
212 If the cache slice is full, the code will try to evict an entry. Only slots that do not have reader…
|
| /mbedtls-latest/scripts/data_files/driver_templates/ |
| D | OS-template-opaque.jinja | 4 * entry_point: the name of the entry point that this function dispatches to.
5 * entry_point_param(driver): the parameters to pass to the entry point.
|
| D | OS-template-transparent.jinja | 4 * entry_point: the name of the entry point that this function dispatches to.
5 * entry_point_param(driver): the parameters to pass to the entry point.
|
| /mbedtls-latest/scripts/ |
| D | generate_visualc_files.pl | 191 (my $entry = $tpl) =~ s/{NAME}/$name/g;
192 $entries .= $entry;
|
| /mbedtls-latest/include/mbedtls/ |
| D | x509_crl.h | 78 …mbedtls_x509_crl_entry entry; /**< The CRL entries containing the certificate revocation times f… member
|
| D | asn1.h | 611 void MBEDTLS_DEPRECATED mbedtls_asn1_free_named_data(mbedtls_asn1_named_data *entry);
|
| /mbedtls-latest/docs/architecture/psa-thread-safety/ |
| D | psa-thread-safety.md | 101 …antees for drivers. Driver entry points may be called concurrently from multiple threads. Threads …
333 …en operations will require a status field protected by a global mutex. On entry, API calls would c…
339 * By default, each driver only has at most one entry point active at any given time. In other words…
345 1. Drivers don't call the core for any operation for which they provide an entry point.
346 2. The core doesn't hold the driver mutex between calls to entry points.
355 …entry points to these must not make a call to the core when handling these calls. (Drivers are sti…
|
| /mbedtls-latest/ |
| D | CONTRIBUTING.md | 12 - [Changelog](#documentation): if needed, please provide a changelog entry.
82 …s://github.com/Mbed-TLS/mbedtls/blob/development/ChangeLog.d/00README.md) entry should be added fo…
|
| D | ChangeLog | 195 in Mbed TLS 3.0, but was not announced in a changelog entry at the time.
376 * Fix possible NULL dereference issue in X509 cert_req program if an entry
378 * Fix possible NULL dereference issue in X509 cert_write program if an entry
561 implementations of FFDH through the driver entry points.
746 some cases involving a missing entry or a full cache.
846 implementations of EC J-PAKE through the driver entry points.
847 * Add new API mbedtls_ssl_cache_remove for cache entry removal by
1043 provided by PSA drivers. (See previous entry for limitation on RSA-PSS
1071 the following entry points: import_key, export_key, export_public_key,
1085 entry point. This entry point is specified in the proposed PSA driver
[all …]
|
| /mbedtls-latest/docs/architecture/testing/ |
| D | driver-interface-test-strategy.md | 129 … a request at runtime and let another driver handle the request. For each entry point, there must …
|
| /mbedtls-latest/tests/suites/ |
| D | test_suite_psa_crypto_driver_wrappers.function | 1520 /* When setup fails, it shouldn't call any further entry points */
1530 /* When setup fails, it shouldn't call any further entry points */
3058 /* Collecting input stage (no driver entry points) */
3071 /* Computation stage (driver entry points) */
|
| D | test_suite_asn1write.function | 502 /* A new entry should have been created. */
|
| D | test_suite_x509parse.data | 2490 X509 CRL ASN1 (TBSCertList, entries present, date in entry invalid)
2512 # 3012 entry 1
2532 X509 CRL ASN1 (TBSCertList, single empty entry at end)
2536 X509 CRL ASN1 (TBSCertList, good entry then empty entry at end)
2540 X509 CRL ASN1 (TBSCertList, missing time in entry)
2544 X509 CRL ASN1 (TBSCertList, missing time in entry at end)
2548 X509 CRL ASN1 (TBSCertList, invalid tag for time in entry)
|
| D | test_suite_psa_crypto_driver_wrappers.data | 458 Cipher driver: negative testing on all entry points
|
