Home
last modified time | relevance | path

Searched refs:new (Results 1 – 25 of 51) sorted by relevance

123

/mbedtls/library/
A Dmemory_buffer_alloc.c300 new->alloc = 0; in buffer_alloc_calloc()
301 new->prev = cur; in buffer_alloc_calloc()
302 new->next = cur->next; in buffer_alloc_calloc()
304 new->trace = NULL; in buffer_alloc_calloc()
305 new->trace_count = 0; in buffer_alloc_calloc()
307 new->magic1 = MAGIC1; in buffer_alloc_calloc()
308 new->magic2 = MAGIC2; in buffer_alloc_calloc()
311 new->next->prev = new; in buffer_alloc_calloc()
319 new->prev_free->next_free = new; in buffer_alloc_calloc()
325 new->next_free->prev_free = new; in buffer_alloc_calloc()
[all …]
/mbedtls/docs/architecture/psa-migration/
A Doutcome-analysis.sh100 new="outcome-$2.csv"
107 sed -n "$sed_cmd" "$new" > skipped-new
109 nb_new=$(wc -l <skipped-new)
114 if diff skipped-ref skipped-new | grep '^> '; then
119 rm skipped-ref skipped-new
A Dtesting.md40 - unit testing of the new API and directly-related APIs - for example:
41 - in `test_suite_pk` we have a new test function `pk_psa_utils` that exercises
47 - in `test_suite_pkwrite` we should have a new test function checking that
50 - integration testing of the new API with each existing API which should
52 - in `programs/ssl/ssl_client2` a new option `key_opaque` that causes the
53 new API to be used, and one or more tests in `ssl-opt.sh` using that.
55 - in `test_suite_x509write` we have a new test function
56 `x509_csr_check_opaque()` checking integration of the new API with the
73 - unit testing of the new API and directly-related APIs - for example:
75 `test_vec_crypt` gained a new parameter `use_psa` and corresponding test
[all …]
A Dstrategy.md17 needs to be changed to use new APIs. For a more detailed account of what's
18 implemented, see `docs/use-psa-crypto.md`, where new APIs are about (G2), and
37 (G1 above), as well as the availability of some new APIs (G2 above).
83 It will then require follow-up work to make use of the new PSA APIs in
138 - Provide a new definition (conditionally on `USE_PSA_CRYPTO`) of wrapper
180 - Provide a new way to set up a context that causes operations on that context
193 There are two variants of this strategy: one where using the new setup
221 - PK (for G2): opt-in use of PSA (new key type)
330 As much as possible, we're trying to create for each algorithm a single new
402 introducing new context types) would provide to users.
[all …]
A Dmd-cipher-dispatch.md22 so that my code keeps working in new minor versions of Mbed TLS.
246 …Pass `MBEDTLS_MD_SHA256` and `md` will dispatch to the legacy code, pass a new constant `MBEDTLS_M…
366 The abstraction layer used by GCM and CCM may either be a new internal module, or a subset of the e…
369 - No need to design, implement and test a new module. (Will need to test the new subset though, as …
371 …new module and Cipher: source-level, and in in particular in builds that still have `CIPHER_C` ena…
374 Possible costs of re-using (a subset of) the existing Cipher API instead of defining a new one:
382 Prototyping both approaches showed better code size savings and cleaner code with a new internal mo…
573 The new module is automatically enabled in `config_adjust_legacy_crypto.h` by modules that need
574 it (namely: CCM, GCM) only when `CIPHER_C` is not available, or the new module
599 Support for dual dispatch in the new internal module `block_cipher` is extremely similar to that in…
[all …]
/mbedtls/programs/ssl/
A Dssl_server2.c791 sni_entry *cur = NULL, *new = NULL; in sni_parse() local
810 GET_ITEM(new->name); in sni_parse()
825 mbedtls_pk_init(new->key); in sni_parse()
866 new->next = cur; in sni_parse()
867 cur = new; in sni_parse()
873 sni_free(new); in sni_parse()
990 psk_entry *cur = NULL, *new = NULL; in psk_parse() local
1007 GET_ITEM(new->name); in psk_parse()
1015 new->next = cur; in psk_parse()
1016 cur = new; in psk_parse()
[all …]
/mbedtls/docs/architecture/
A Dpsa-crypto-implementation-structure.md75 ## How to implement a new cryptographic mechanism
77 Summary of files to modify when adding a new algorithm or key type:
80 …to_values.h` or `include/psa/crypto_extra.h` — [New functions and macros](#new-functions-and-macro…
86 * [ ] `tests/suites/test_suite_psa_crypto_metadata.data` — [New functions and macros](#new-function…
87 …tes/test_suite_psa_crypto_metadata.function` — [New functions and macros](#new-functions-and-macro…
92 Summary of files to modify when adding new API functions:
94 …to_sizes.h`, or `include/psa/crypto_extra.h` — [New functions and macros](#new-functions-and-macro…
111 If a mechanism requires new functions, they should follow the design guidelines in the PSA Cryptogr…
146 When implementing a new algorithm or key type, there are typically things to change in `library/cry…
162 When adding a new key type or algorithm:
[all …]
/mbedtls/tests/data_files/dir-maxpath/
A Dlong.sh15 $OPENSSL req -new -x509 -subj "/C=UK/O=mbed TLS/CN=CA00" $OPT \
28 $OPENSSL req -new -subj "/C=UK/O=mbed TLS/CN=CA${ME}" \
/mbedtls/
A DCONTRIBUTING.md35 …main development branch where new features are added, need to be justifiable by either being a sig…
37 …different prototype, or different documented behavior), create a new function with a new name with…
48 … to that LTS branch. If a bug fix introduces a change to the API such as a new function, the fix s…
49 1. If a contribution is a new feature or enhancement, no backporting is required. Exceptions to thi…
91 All new files should include the standard SPDX license identifier where possible, i.e. "SPDX-Licens…
93 …utions is retained by the original authors of the code. Where possible for new files, this should …
A DBRANCHES.md11 as well as all the new features and bug fixes and security fixes.
48 Note that new releases of Mbed TLS may extend the API. Here are some
56 when a new error condition arises.
61 addition of a new feature.
A DChangeLog100 * The new functions mbedtls_pk_get_psa_attributes() and
113 * Add new accessor to expose the private group id member of
124 * The new functions mbedtls_pk_copy_from_psa() and
127 * Add new accessors to expose the private session-id,
130 Add new accessor to expose the ciphersuite-id of
673 ECJPAKE key exchange, using the new API function
1518 new function mbedtls_gcm_update_ad().
3024 * The new functions mbedtls_ctr_drbg_update_ret() and
3028 applications use the new functions.
3663 the new configuration flag MBEDTLS_ECJPAKE_ALT.
[all …]
A D.pylintrc57 # logging-too-many-args (Pylint supports new-style formatting if
/mbedtls/.github/
A Dpull_request_template.md9 Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new …
26 - please do not force-push to update your PR - just add new commit(s)
/mbedtls/docs/
A Duse-psa-crypto.md7 - enables new APIs for using keys handled by PSA Crypto, such as
64 reasons, we can't extend its scope. However, new modules in the library, such
87 using the new API in order to get the benefits; it can then pass the
107 the new APIs to get the benefits.
120 the new APIs to get the benefits.
124 There is a new API function `mbedtls_cipher_setup_psa()` to set up a context
A D3.0-migration-guide.md152 Please use the new names directly in your code; `scripts/rename.pl` (from any
238 * `mbedtls_gcm_starts()` now only sets the mode and the nonce (IV). Call the new function `mbedtls_…
475 in order to match the new signature.
513 API were removed from version 1.0 of specification. Please switch to the new
531 and explain your need; we'll consider adding a new API in a future version.
536 multi-part operations. Five new API functions have been defined:
744 The new single option `MBEDTLS_SSL_CID_TLS1_3_PADDING_GRANULARITY` can be used
761 Those APIs have been removed and replaced by the new API
777 For users which do not rely on raw keys and IV, adjusting to the new
1003 This option has been removed and a new function with similar functionality has
[all …]
/mbedtls/ChangeLog.d/
A D00README.md13 * New features in the library, new sample programs, or new platform support.
81 consequences of the bug, not how the bug was fixed. For a new feature, explain
/mbedtls/tests/data_files/
A DMakefile289 $(OPENSSL) req -new -config $(test_ca_config_file) -key test-int-ca2.key \
293 $(OPENSSL) req -new -config $(test_ca_config_file) -key test-int-ca3.key \
359 $(OPENSSL) req -new -key server7.key -subj "/C=NL/O=PolarSSL/CN=localhost" -out $@
455 $(OPENSSL) req -x509 -new -subj "/C=UK/O=mbed TLS/CN=mbed TLS Test intermediate CA 3" \
544 $(OPENSSL) req -new -subj "/C=NL/O=PolarSSL/CN=localhost" \
1512 $(OPENSSL) req -new -subj "/C=NL/O=PolarSSL/CN=localhost" \
1562 $(OPENSSL) req -new -subj "/C=NL/O=PolarSSL/CN=localhost" \
1571 $(OPENSSL) req -new -subj "/CN=selfsigned-child/OU=testing/O=PolarSSL/C=NL" \
1826 $(OPENSSL) req -new -subj "/C=NL/O=PolarSSL/CN=localhost" \
1838 $(OPENSSL) req -new -subj "/C=NL/O=PolarSSL/CN=localhost" \
[all …]
/mbedtls/tests/suites/
A Dtest_suite_asn1write.data385 Store named data: new, val_len=0
388 Stored named data: new, val_len=0, val=NULL
391 Store named data: new, val_len=4
394 Store named data: new, val_len=4, val=NULL
A Dtest_suite_psa_crypto_slot_management.data220 # Eviction from a key slot to be able to import a new persistent key.
221 Key slot eviction to import a new persistent key
224 # Eviction from a key slot to be able to import a new volatile key.
225 Key slot eviction to import a new volatile key
A Dtest_suite_asn1parse.function135 /* Allocate a new buffer of exactly the length to parse each time.
248 /* Allocate a new buffer of exactly the length to parse each time.
760 mbedtls_asn1_named_data *new = NULL;
761 TEST_CALLOC(new, 1);
762 new->next = head;
763 head = new;
A Dtest_suite_asn1write.function502 /* A new entry should have been created. */
529 unsigned char *new_val = (unsigned char *) "new value";
571 const unsigned char *new_val = (unsigned char *) "new value";
/mbedtls/scripts/
A Dci.requirements.txt5 # Use a known version of Pylint, because new versions tend to add warnings
/mbedtls/tests/docker/bionic/
A DDockerfile81 # Build a new openssl binary for ARIA/CHACHA20 support
86 …&& ./config --prefix=/usr/local/openssl-1.1.1a -Wl,--enable-new-dtags,-rpath,'${LIBRPATH}' no-shar…
/mbedtls/docs/architecture/psa-thread-safety/
A Dpsa-thread-safety.md5 …tions which only ever call PSA functions from a single thread are not affected by this new feature.
69 …suppose two calls are executed concurrently which both attempt to create a new key with the same k…
78 …ad, or which protect all PSA calls using a mutex, are not affected by this new feature. If an appl…
82 …ndition variables](#condition-variables) for discussion about implementing new primitives in futur…
92 …ional requirement for persistent keys: any thread can immediately create a new key with the same i…
204 To load a new key into a slot, the following internal utility functions are used:
208 …SLOT_FULL` and releases the mutex. Upon success, any thread is immediately able to use the new key.
261 …gle-threaded, tests in such a way that tests concurrency. We need to write new test suites for con…
308 …ional requirement for persistent keys: any thread can immediately create a new key with the same i…
353 2. Provide a new public API that drivers can safely call.
/mbedtls/programs/
A DREADME.md24 …riter.c): loads a PEM or DER public key or private key file and writes it to a new PEM or DER file.
83 …the library, and most applications require only a few features. To write a new application, we rec…

Completed in 53 milliseconds

123