Lines Matching refs:implementation

103 the following implementations: AES-NI, assembler implementation, or
105 which cipher implementation is used? The answer to that question is the
106 priority number assigned to each cipher implementation by the kernel
109 implementations providing an implementation with that name and selects
110 the implementation with the highest priority.
113 implementation and thus does not want to rely on the priority-based
115 the cipher implementation to register a unique name in addition to
117 sure to refer to the intended cipher implementation.
133 -  module: the kernel module providing the cipher implementation (or
136 -  priority: the priority value of the cipher implementation
162       the cipher implementation)
165       an ECDH or DH implementation
226    an ECDH or DH implementation
252 cipher implementation for the given cipher name. That means, even when a
261 implementation may use many layers and indirections. This section shall
282 seqiv.c). The generic implementation serves as an example showing the
288 the AES-NI implementation, the CTR mode, the GHASH implementation and
289 the AES cipher are all merged into one cipher implementation registered
298 crypto API for the cipher implementation type.
348    In case of GCM, the SEQIV implementation is registered as GIVCIPHER
363    The GCM implementation is responsible to invoke the CTR mode AES and
367 3. The GCM AEAD cipher type implementation now invokes the SKCIPHER API
371    implementation of AES is instantiated. The cipher handle for AES is
374    That means that the SKCIPHER implementation of CTR(AES) only
376    chaining operation, the CIPHER implementation of AES is invoked.
381 5. The GCM AEAD implementation also invokes the GHASH cipher
382    implementation via the AHASH API.
406 implementation:
431    implementation performs its operation as needed.
437    At one time, the HMAC implementation requires a SHA256 operation