Lines Matching full:api

1 Kernel Crypto API Architecture
7 The kernel crypto API provides different API calls for the following
23 The kernel crypto API provides implementations of single block ciphers
24 and message digests. In addition, the kernel crypto API provides
60 The kernel crypto API provides synchronous and asynchronous API
63 When using the synchronous API operation, the caller invokes a cipher
64 operation which is performed synchronously by the kernel crypto API.
66 Therefore, the kernel crypto API calls work like regular function calls.
67 For synchronous operation, the set of API calls is small and
70 Asynchronous operation is provided by the kernel crypto API which
74 must provide a callback function the kernel crypto API can invoke to
77 appropriate locking around its data. The kernel crypto API does not
81 Crypto API Cipher References And Priority
101 The kernel crypto API may provide multiple implementations of a template
104 straight C. Now, when using the string "aes" with the kernel crypto API,
107 crypto API. When a caller uses the string to refer to a cipher during
108 initialization of a cipher handle, the kernel crypto API looks up all
114 selection. To accommodate this scenario, the kernel crypto API allows
127    allocation API calls (all names listed above are examples for such
131    cipher allocation API calls
181 with the length of the provided key. Thus, the kernel crypto API does
228 limits the search the kernel crypto API can perform for a suitable
231 the kernel crypto API may not select it due to the used type and mask
234 Internal Structure of Kernel Crypto API
237 The kernel crypto API has an internal structure where a cipher
239 help to clarify how the kernel crypto API uses various components to
249 The following ASCII art decomposes the kernel crypto API layers when
260 complete logic of the kernel crypto API.
264 kernel crypto API cannot be decomposed into layers any more. In case of
267 with the kernel crypto API. In this case, the concept described by the
269 the individual sub-components by the kernel crypto API is not done any
273 obtained from the kernel crypto API. Each block is accessed by the
274 caller or by other blocks using the API functions defined by the kernel
275 crypto API for the cipher implementation type.
282 uses the API applicable to the cipher type specified for the block.
287     kernel crypto API                                |   IPSEC Layer
327 2. Now, SEQIV uses the AEAD API function calls to invoke the associated
340 3. The GCM AEAD cipher type implementation now invokes the SKCIPHER API
351 4. The SKCIPHER of CTR(AES) now invokes the CIPHER API with the AES
355    implementation via the AHASH API.
384     kernel crypto API            |       Caller
403 1. The AHASH API functions are invoked by the caller. The HMAC
413 2. The HMAC instance now invokes the SHASH API with the SHA256 cipher