MAJOR=7
MINOR=5
DEVNAME=vcs5
-ˆÆË
‚ €¿È -# SPDX-License-Identifier: GPL-2.0
CC := $(CROSS_COMPILE)gcc
CFLAGS := -I../../usr/include
PROGS := getdelays procacct
all: $(PROGS)
clean:
rm -fr $(PROGS)
/ˆ
ƒ M½Ç¿È ² /
Index of /anon_sym/anon/sys/dev/char/4:62/subsystem/tty49
Index of /anon_sym/anon/sys/dev/char/4:62/subsystem/tty49
1ˆl–ß=¿J •2ÛB‚ œP@¸Ènå1hßÌ
0ÀÉ 3ˆÇÌ
„ Ï<Ï_†I|¥+ÁÊ ?÷ 3/* SPDX-License-Identifier: GPL-2.0-or-later */
/*
* AEAD: Authenticated Encryption with Associated Data
*
* Copyright (c) 2007-2015 Herbert Xu
*/
#ifndef _CRYPTO_AEAD_H
#define _CRYPTO_AEAD_H
#include
#include
#include
#include
/**
* DOC: Authenticated Encryption With Associated Data (AEAD) Cipher API
*
* The AEAD cipher API is used with the ciphers of type CRYPTO_ALG_TYPE_AEAD
* (listed as type "aead" in /proc/crypto)
*
* The most prominent examples for this type of encryption is GCM and CCM.
* However, the kernel supports other types of AEAD ciphers which are defined
* with the following cipher string:
*
* authenc(keyed message digest, block cipher)
*
* For example: authenc(hmac(sha256), cbc(aes))
*
* The example code provided for the symmetric key cipher operation
* applies here as well. Naturally all *skcipher* symbols must be exchanged
* the *aead* pendants discussed in the following. In addition, for the AEAD
* operation, the aead_request_set_ad function must be used to set the
* pointer to the associated data memory location before performing the
* encryption or decryption operation. In case of an encryption, the associated
* data memory is filled during the encryption operation. For decryption, the
* associated data memory must contain data that is used to verify the integrity
* of the decrypted data. Another deviation from the asynchronous block cipher
* operation is that the caller should explicitly check for -EBADMSG of the
* crypto_aead_decrypt. That error indicates an authentication error, i.e.
* a breach in the integrity of the message. In essence, that -EBADMSG error
* code is the key bonus an AEAD cipher has over "standard" block chaining
* modes.
*
* Memory Structure:
*
* The source scatterlist must contain the concatenation of
* associated data || plaintext or ciphertext.
*
* The destination scatterlist has the same layout, except that the plaintext
* (resp. ciphertext) will grow (resp. shrink) by the authentication tag size
* during encryption (resp. decryption).
*
* In-place encryption/decryption is enabled by using the same scatterlist
* pointer for both the source and destination.
*
* Even in the out-of-