| /src/crypto/openssl/doc/man7/ |
| H A D | EVP_KEM-ML-KEM.pod | 20 The OpenSSL ML-KEM encapsulation mechanism can only be modified by 21 setting randomness during encapsulation, this enables testing, as per 26 When this parameter is not set, encapsulation proceeds as per FIPS 203,
|
| H A D | EVP_PKEY-ML-KEM.pod | 117 is performed with a random entropy value for the encapsulation step. 118 Setting the parameter to C<fixed>, still runs the test, but the encapsulation 188 decapsulation key B<dk> and the encapsulation key B<ek>. 196 the 64-byte FIPS 204 seed B<(d, z)> without any ASN.1 encapsulation. 203 the FIPS 204 decapsulation key B<dk> without any ASN.1 encapsulation.
|
| H A D | provider-kem.pod | 131 encapsulation given a provider side asymmetric kem context in the I<ctx> 144 OSSL_FUNC_kem_encapsulate() performs the actual encapsulation itself.
|
| H A D | EVP_PKEY-ML-DSA.pod | 165 the 32-byte FIPS 204 seed B<ξ> without any ASN.1 encapsulation. 172 the FIPS 204 secret key B<sk> without any ASN.1 encapsulation.
|
| H A D | provider-base.pod | 587 I<key exchange> (KEX) or I<key encapsulation method> (KEM) during a TLS 624 or I<key encapsulation method> (KEM), as implied by the optional 640 mode (0, default) or in I<key encapsulation method> (KEM) mode (1).
|
| /src/crypto/openssl/doc/designs/ |
| H A D | ML-KEM.md | 24 These are then used in key generation, encapsulation and decapsulation. 43 subsequent computations (encapsulation). 47 During encapsulation (typically performed by servers), it is in principle 58 demand during encapsulation. 78 encapsulation/decapsulation functions operate on "extended keys" in the 106 For the encapsulation operation, a test-only option exists to bypass the random
|
| /src/crypto/openssl/doc/man3/ |
| H A D | EVP_PKEY_encapsulate.pod | 6 - Key encapsulation using a KEM algorithm with a public key 22 context I<ctx> for an encapsulation operation and then sets the I<params> 29 key that is used during encapsulation. 31 The EVP_PKEY_encapsulate() function performs a public key encapsulation
|
| H A D | EVP_KEM_free.pod | 36 as key encapsulation and decapsulation. 73 parameters that can be retrieved or set by a key encapsulation algorithm using
|
| H A D | OSSL_HPKE_CTX_new.pod | 91 key that supports combinations of a key encapsulation method (KEM), a key 181 supplied before the encapsulation/decapsulation operation will work. 253 encapsulation step, the sender can then make one or more calls to 264 single-use ephemeral private value created as part of the encapsulation 289 In order to enable encapsulation, the recipient needs to make it's public value 353 the sender's authentication private/public values into the encapsulation and 404 A baseline nonce value is established based on the encapsulation or
|
| H A D | RSA_check_key.pod | 69 completely violating encapsulation and object-orientation in the process).
|
| H A D | EVP_PKEY_set1_encoded_public_key.pod | 33 support key exchange or key encapsulation.
|
| H A D | PEM_read.pod | 70 <type>-----" is returned via the B<name> argument, any encapsulation headers
|
| /src/contrib/llvm-project/lld/docs/ELF/ |
| H A D | start-stop-gc.rst | 8 …>>> the encapsulation symbol needs to be retained under --gc-sections properly; consider -z nostar… 13 ``__start_meta`` and ``__stop_meta`` are sometimes called encapsulation
|
| /src/contrib/tcpdump/ |
| H A D | print-lspping.c | 337 nd_uint16_t encapsulation; member 809 … GET_BE_U_2(subtlv_ptr.lspping_tlv_targetfec_subtlv_l2vpn_endpt->encapsulation)), in lspping_print() 810 … GET_BE_U_2(subtlv_ptr.lspping_tlv_targetfec_subtlv_l2vpn_endpt->encapsulation)); in lspping_print()
|
| H A D | INSTALL.md | 107 l2vpn.c - L2VPN encapsulation value-to-name table 108 l2vpn.h - L2VPN encapsulation definitions
|
| /src/lib/libc/net/ |
| H A D | protocols | 101 ipip 94 IPIP # Yet Another IP encapsulation 105 encap 98 ENCAP # Yet Another IP encapsulation
|
| /src/crypto/openssl/doc/man1/ |
| H A D | openssl-list.pod.in | 98 =item Key encapsulation methods (KEM) 203 Display a list of key encapsulation algorithms.
|
| H A D | openssl-pkeyutl.pod.in | 102 Specifies the shared-secret output filename for when performing encapsulation 206 derived shared-secret value generated in the encapsulation process. 218 At the API level, encapsulation and decapsulation are also supported for a few 547 The ML-KEM algorithms support encapsulation and decapsulation only. 548 The encapsulation operation supports a B<hexikme>:I<entropy> option, 651 Generate an ML-KEM key pair and use it for encapsulation:
|
| H A D | openssl-speed.pod.in | 105 Benchmark KEM algorithms: key generation, encapsulation, decapsulation.
|
| /src/sys/dev/mlx5/mlx5_fpga/ |
| H A D | mlx5_ifc_fpga.h | 385 u8 encapsulation[0x20]; member
|
| /src/contrib/wpa/wpa_supplicant/ |
| H A D | README-WPS | 337 encapsulation to be included). This data needs to be written to an NFC 348 without NDEF encapsulation) can be delivered to wpa_supplicant using the 390 requests additional NDEF encapsulation to be included). This data needs
|
| H A D | eap_testing.txt | 7 encapsulation/decapsulation) into wpa_supplicant. 241 limit with AVP encapsulation and TLS tunneling. Note: EAP-PEAP/TLS
|
| /src/crypto/openssl/doc/HOWTO/ |
| H A D | keys.txt | 108 An ML-KEM key can be used for decapsulation (and encapsulation via the public
|
| /src/contrib/wpa/hostapd/ |
| H A D | README-WPS | 323 encapsulation to be included). This data needs to be written to an NFC 330 NDEF encapsulation) can be delivered to hostapd using the
|
| H A D | README | 140 Authentication Server. hostapd supports RADIUS encapsulation of EAP 184 Authenticator and RADIUS encapsulation between the Authenticator and
|