| /mbedtls-development/tests/scripts/ |
| A D | check_test_cases.py | 61 file_name, line_number, description): argument
110 description = m.group(1)
152 file_name, line_number, description): argument
156 if description in seen:
159 seen[description])
161 if re.search(br'[\t;]', description):
165 if re.search(br'[^ -~]', description):
168 if len(description) > 66:
171 len(description))
172 seen[description] = line_number
[all …]
|
| A D | generate_psa_tests.py | 341 description: str,
353 self.description = description #type: str
423 description = 'lifetime: ' + short
429 description=description)
457 description = 'usage' + extra_desc + ': ' + short
464 description=description)
475 description=description)
522 description=description)
544 description='alg: ' + descr)
632 description=description)
[all …]
|
| A D | analyze_outcomes.py | 62 file_name, _line_number, description): argument
65 key = ';'.join([base_name, description.decode('utf-8')])
118 parser = argparse.ArgumentParser(description=__doc__)
|
| A D | list_internal_identifiers.py | 38 description=(
|
| A D | psa_collect_statuses.py | 115 parser = argparse.ArgumentParser(description=globals()['__doc__'])
|
| A D | test_config_script.py | 167 parser = argparse.ArgumentParser(description=__doc__,
|
| A D | test_psa_constant_names.py | 156 parser = argparse.ArgumentParser(description=globals()['__doc__'])
|
| A D | check_files.py | 398 parser = argparse.ArgumentParser(description=__doc__)
|
| /mbedtls-development/scripts/mbedtls_dev/ |
| A D | test_case.py | 39 def __init__(self, description: Optional[str] = None):
41 self.description = description #type: Optional[str]
49 def set_description(self, description: str) -> None:
50 self.description = description
62 if self.description is None:
76 assert self.description is not None # guide mypy
81 out.write(self.description + '\n')
|
| /mbedtls-development/scripts/ |
| A D | generate_errors.pl | 93 my $description = (defined($before) ? $before : $after);
94 $description =~ s/^\s+//;
95 $description =~ s/\n( *\*)? */ /g;
96 $description =~ s/\.?\s+$//;
97 push @matches, [$name, $value, $description];
120 my ($error_name, $error_code, $description) = @$match;
125 $description =~ s/\\/\\\\/g;
207 "${white_space} return( \"$module_name - $description\" );\n"
|
| A D | config.py | 432 parser = argparse.ArgumentParser(description="""
481 def add_adapter(name, function, description): argument
482 subparser = subparsers.add_parser(name, help=description)
|
| A D | code_size_compare.py | 182 description=(
|
| A D | assemble_changelog.py | 491 parser = argparse.ArgumentParser(description=__doc__)
|
| /mbedtls-development/docs/architecture/testing/ |
| A D | test-framework.md | 13 …description which succinctly describes for a human audience what the test does. The first non-comm…
17 …s must be unique within a `.data` file. If you can't think of a better description, the convention…
22 * Make the description descriptive. “foo: x=2, y=4” is more descriptive than “foo #2”. “foo: 0<x<y,…
23 * Avoid changing the description of an existing test case without a good reason. This breaks the tr…
33 …ase in `ssl-opt.sh` has a description which succinctly describes for a human audience what the tes…
35 …or [unit test descriptions](#unit-test-descriptions). In addition, the description must be written…
53 * **Platform**: a description of the platform, e.g. `Linux-x86_64` or `Linux-x86_64-gcc7-msan`.
54 * **Configuration**: a unique description of the configuration (`mbedtls_config.h`).
56 * **Test case**: the description of the test case.
|
| /mbedtls-development/docs/proposed/ |
| A D | psa-driver-developer-guide.md | 25 … linkage, and to declare these functions in a **driver description file**. The driver description …
27 …description file is JSON. The structure of this JSON file is specified in the section [“Driver des…
31 * A driver description file (in JSON format).
32 …g the types required by the driver description. The names of these header files is declared in the…
33 … for the target platform defining the functions required by the driver description. Implementation…
|
| A D | psa-driver-integration-guide.md | 16 Concretely speaking, a driver consists of one or more **driver description files** in JSON format a…
29 2. Pass the driver description files through the Make variable `PSA_DRIVERS` when building the libr…
|
| A D | psa-driver-interface.md | 49 …a driver description file is JSON. The structure of this JSON file is specified in the section [“D…
53 * A driver description file (in JSON format).
54 …g the types required by the driver description. The names of these header files are declared in th…
59 ### Driver description syntax
61 The concrete syntax for a driver description file is JSON.
63 #### Driver description list
67 #### Driver description top-level element
69 A driver description is a JSON object containing the following properties:
74 * `"capabilities"` (mandatory, array of [capabilities](#driver-description-capability)).
80 ### Driver description capability
[all …]
|
| /mbedtls-development/ChangeLog.d/ |
| A D | 00README.md | 36 * Change description.
37 * Another change description.
40 * Yet another change description. This is a long change description that
42 * Yet again another change description.
|
| /mbedtls-development/library/ |
| A D | oid.c | 48 #define OID_DESCRIPTOR(s, name, description) { ADD_LEN(s), name, description } argument
51 #define OID_DESCRIPTOR(s, name, description) { ADD_LEN(s) } argument
318 …tls_oid_get_extended_key_usage, mbedtls_oid_descriptor_t, ext_key_usage, const char *, description)
327 …et_certificate_policies, mbedtls_oid_descriptor_t, certificate_policies, const char *, description)
433 …T_DESCRIPTOR_ATTR1(mbedtls_oid_get_sig_alg_desc, oid_sig_alg_t, sig_alg, const char *, description)
|
| /mbedtls-development/tests/suites/ |
| A D | test_suite_asn1parse.function | 181 const char *description;
184 /* Value returned by traverse_callback if description runs out. */
196 const char *rest = state->description;
218 state->description = rest;
582 const char *description,
585 /* The description string is a comma-separated list of integers.
595 const char *rest = description;
644 const char *description,
647 /* The description string is a comma-separated list of integers.
655 traverse_state_t traverse_state = {input->x, description};
[all …]
|
| /mbedtls-development/programs/test/ |
| A D | udp_proxy.c | 394 const char *description; member
411 ellapsed_time(), buf->description, in ctx_buffer_flush()
907 outbuf[0].description = "S <- C"; in main()
912 outbuf[1].description = "S -> C"; in main()
|
| /mbedtls-development/docs/architecture/ |
| A D | psa-crypto-implementation-structure.md | 17 …ftware cryptographic functionalities can be described by a JSON driver description file as defined…
18 * Along with JSON driver description files, the PSA driver specification defines the deliverables f…
52 …` functions are generated by the build system based on the JSON driver description files of the va…
|
| /mbedtls-development/include/mbedtls/ |
| A D | oid.h | 438 const char *MBEDTLS_PRIVATE(description); /*!< human friendly description */
|
| /mbedtls-development/ |
| A D | Makefile | 154 …genhtml --title "mbed TLS" --description-file descriptions --keep-descriptions --legend --branch-c…
|
| /mbedtls-development/doxygen/ |
| A D | mbedtls.doxyfile | 39 # Using the PROJECT_BRIEF tag one can provide an optional one line description
41 # a quick idea about the purpose of the project. Keep the description short.
89 # the brief description of a member or function before the detailed description.
95 # This tag implements a quasi-intelligent brief description abbreviator
119 # description.
164 # comment as the brief description. If set to NO, the JavaDoc
166 # (thus requiring an explicit @brief command for a brief description.)
172 # comment as the brief description. If set to NO, the comments
174 # an explicit \brief command for a brief description.)
180 # comments) as a brief description. This used to be the default behaviour.
[all …]
|