Lines Matching refs:access

356    * Fix rare concurrent access bug where attempting to operate on a
528    * Add getter (mbedtls_ssl_session_get_ticket_creation_time()) to access
566    * Add protection for multithreaded access to the PSA keystore and protection
567      for multithreaded access to the the PSA global state, including
837    * Add getter (mbedtls_ssl_cache_get_timeout()) to access
839    * Add getter (mbedtls_ssl_get_hostname()) to access
841    * Add getter (mbedtls_ssl_conf_get_endpoint()) to access
884      has access to precise timing measurements.
1151      arguments, access uninitialized memory in some cases. Fixes #6700 (which
1332    * Fix an issue where an adversary with access to precise enough information
1474    * Add a function to access the protocol version from an SSL context in a
1488    * Add function mbedtls_timing_get_final_delay() to access the private
1498    * Add the function mbedtls_ssl_get_own_cid() to access our own connection id
1514    * Add the function mbedtls_x509_crt_has_ext_type() to access the ext types
2032    * Direct access to fields of structures declared in public headers is no
2195    * Fix an issue where an adversary with access to precise enough information
2200    * Fix an issue where an adversary with access to precise enough timing
2424      making access aceess to them use constant flow code.
2674      Encrypt-then-Mac extension, use constant code flow memory access patterns
2679      if they have access to fine-grained measurements. In particular, this
2684      Diffie-Hellman. An adversary with precise enough timing and memory access
2781      f_rng argument. An attacker with access to precise enough timing and
2782      memory access information (typically an untrusted operating system
2880    * Fix side channel in ECC code that allowed an adversary with access to
2881      precise enough timing and memory access information (typically an
3435    * Fix timing variations and memory access variations in RSA PKCS#1 v1.5
3445      via branching and memory access patterns. An attacker who could submit
3473      to trigger a memory access up to 64KiB beyond the incoming message buffer,
5375    * Possible remotely-triggered out-of-bounds memory access fixed (found by
5460    * Possible remotely-triggered out-of-bounds memory access fixed (found by