1KCAPI_CIPHER_DECRYPT(3)      Programming Interface     KCAPI_CIPHER_DECRYPT(3)
2
3
4

NAME

6       kcapi_cipher_decrypt - decrypt data (synchronous one shot)
7

SYNOPSIS

9       int32_t kcapi_cipher_decrypt(struct kcapi_handle * handle,
10                                    const uint8_t * in, uint32_t inlen,
11                                    const uint8_t * iv, uint8_t * out,
12                                    uint32_t outlen, int access);
13

ARGUMENTS

15       handle
16           [in] cipher handle
17
18       in
19           [in] ciphertext data buffer
20
21       inlen
22           [in] length of in buffer
23
24       iv
25           [in] IV to be used for cipher operation
26
27       out
28           [out] plaintext data buffer
29
30       outlen
31           [in] length of out bufferS
32
33       access
34           [in] kernel access type (KCAPI_ACCESS_HEURISTIC - use internal
35           heuristic for fastest kernel access; KCAPI_ACCESS_VMSPLICE - use
36           vmsplice access; KCAPI_ACCESS_SENDMSG - sendmsg access)
37

DESCRIPTION

39       It is perfectly legal to use the same buffer as the plaintext and
40       ciphertext pointers. That would mean that after the encryption
41       operation, the ciphertext is overwritten with the plaintext.
42
43       The memory should be aligned at the page boundary using
44       posix_memalign(sysconf(_SC_PAGESIZE)), If it is not aligned at the page
45       boundary, the vmsplice call may not send all data to the kernel.
46
47       The IV buffer must be exactly kcapi_cipher_ivsize bytes in size.
48
49       return number of bytes decrypted upon success; a negative errno-style
50       error code if an error occurred
51

AUTHOR

53       Stephan Mueller <smueller@chronox.de>
54           Author.
55

57libkcapi Manual 1.1.1             August 2018          KCAPI_CIPHER_DECRYPT(3)
Impressum