Lines Matching refs:crypto

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
36 See /proc/crypto and search for "name". For example:
60 The kernel crypto API provides synchronous and asynchronous API
64 operation which is performed synchronously by the kernel crypto API.
66 Therefore, the kernel crypto API calls work like regular function calls.
68 conceptually similar to any other crypto library.
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
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
119 The list of available ciphers is given in /proc/crypto. However, that
121 ciphers. Each block listed in /proc/crypto may contain the following
194 with the length of the provided key. Thus, the kernel crypto API does
222    together with an IV generator (see geniv field in the /proc/crypto
251 limits the search the kernel crypto API can perform for a suitable
254 the kernel crypto API may not select it due to the used type and mask
260 The kernel crypto API has an internal structure where a cipher
262 help to clarify how the kernel crypto API uses various components to
272 The following ASCII art decomposes the kernel crypto API layers when
283 complete logic of the kernel crypto API.
287 kernel crypto API cannot be decomposed into layers any more. In case of
290 with the kernel crypto API. In this case, the concept described by the
292 the individual sub-components by the kernel crypto API is not done any
296 obtained from the kernel crypto API. Each block is accessed by the
298 crypto API for the cipher implementation type.
310     kernel crypto API                                |   IPSEC Layer
411     kernel crypto API            |       Caller