Searched refs:g (Results 1 – 25 of 41) sorted by relevance
12
17 #define MBEDTLS_ASN1_CHK_ADD(g, f) \ argument23 (g) += ret; \26 #define MBEDTLS_ASN1_CHK_CLEANUP_ADD(g, f) \ argument32 (g) += ret; \
38 g++-multilib \71 # Build OPENSSL as 1.0.2g73 && wget https://www.openssl.org/source/old/1.0.2/openssl-1.0.2g.tar.gz -qO- | tar xz \74 && cd openssl-1.0.2g \75 && ./config --openssldir=/usr/local/openssl-1.0.2g no-shared \79 ENV OPENSSL=/usr/local/openssl-1.0.2g/bin/openssl
112 DH load parameters from PEM file (1024-bit, g=2)116 DH load parameters from PEM file (2048-bit, large g, privateValueLength)120 DH load parameters from DER file (2048-bit, large g, privateValueLength)
11 # can be avoided with e.g. ASAN_OPTIONS=allocator_may_return_null=1,
263 void dhm_file(char *filename, char *p, char *g, int len)272 TEST_ASSERT(mbedtls_test_read_mpi(&G, g) == 0);
7 # randomization for (e.g.) blinding. An external implementation could use
28 void printf_int(char *format, /* any format expecting one int argument, e.g. "%d" */
239 * E.g. start by processing bytes individual bytes, then 2-byte chunks,
875 * key in creation order (e.g. 0 means the first key that was created).876 * It can also be a negative value to count in reverse order (e.g.898 /* Account for any system-created volatile key, e.g. for the RNG. */
242 * from another directory (e.g. the project root) and still access
47 #define MBEDTLS_BYTES_TO_T_UINT_8(a, b, c, d, e, f, g, h) \ argument49 MBEDTLS_BYTES_TO_T_UINT_4(e, f, g, h)53 #define MBEDTLS_BYTES_TO_T_UINT_8(a, b, c, d, e, f, g, h) \ argument60 ((mbedtls_mpi_uint) (g) << 48) | \
577 uint8x16_t c, d, e, f, g, n, o; in poly_mult_reduce() local585 g = vextq_u8(ZERO, e, 8); /* : :g1:00 = e1:00 */ in poly_mult_reduce()588 return veorq_u8(o, g); /* = o1:o0 + g1:00 */ in poly_mult_reduce()
477 #define P(a, b, c, d, e, f, g, h, x, K) \ argument480 local.temp1 = (h) + S3(e) + F1((e), (f), (g)) + (K) + (x); \
622 #define P(a, b, c, d, e, f, g, h, x, K) \ in mbedtls_internal_sha512_process_c() argument625 local.temp1 = (h) + S3(e) + F1((e), (f), (g)) + (K) + (x); \ in mbedtls_internal_sha512_process_c()
68 g = translate_gnutls(s)69 self.assertEqual(g, g_exp)
64 * Expected errors (e.g. `PSA_ERROR_INVALID_SIGNATURE` from a signature verification method).87 * This must be done for each possible flow, including error cases (e.g. a key creation that fails m…90 * Check both that the storage has the expected content (this can be done by e.g. using a key that i…103 * Run at least one test application (e.g. the Mbed OS TLS example).
59 * **Platform**: a description of the platform, e.g. `Linux-x86_64` or `Linux-x86_64-gcc7-msan`.
115 Constants (algorithm identifiers, key type identifiers, etc.) and associated destructor macros (e.g…146 … or key type, there are typically things to change in `library/crypto.c` (e.g. buffer size calcula…170 * Potential edge cases (e.g. data less/equal/more than the block size, number equal to zero in asym…171 * Tests with invalid keys (e.g. wrong size or format).172 * Tests with invalid data (e.g. wrong size or format, output buffer too small, invalid padding).
250 s/\b(?=MBEDTLS_|PSA_)/LIBTESTDRIVER1_/g; \251 s/\b(?=mbedtls_|psa_)/libtestdriver1_/g;
136 # But allow a space in the case of e.g. char * const x;145 # Force exactly 1 space between a statement keyword (e.g. 'if') and an opening parenthesis
60 …files (e.g. `test_suite_rsa.c`). These files are generated from a `function file` (e.g. `suites/te…
22 API compatibility in the `main` branch across minor version changes (e.g.24 compatibility on major version changes (e.g. from 3.x to 4.0). We also maintain
243 …les (e.g. `test\_suite\_mpi.c`). These files are generated from a `function file` (e.g. `suites/te…
9 Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new …
100 * Software implementations of constructed cryptographic mechanisms (e.g. HMAC, CTR_DRBG, RSA (calli…219 * How the mechanism is encoded (e.g. `mbedtls_md_type_t` vs `const *mbedtls_md_info_t` vs `psa_algo…221 * How to obtain metadata about algorithms (e.g. hash/MAC/tag size, key size).254 …g. `MBEDTLS_SHA256_C` is enabled, then I want RSA-PSS to support SHA-256. I don't care about negat…255 * For a caller in the PSA domain: if e.g. `PSA_WANT_ALG_SHA_256` is enabled, then I want RSA-PSS to…284 …lerators available to legacy callers that call any legacy hash interface, e.g. `md.h` or `shaX.h`.…
