Home
last modified time | relevance | path

Searched refs:IV (Results 1 – 25 of 46) sorted by relevance

12

/Linux-v4.19/Documentation/crypto/
Dapi.rst7 future. To obtain the functionality of an AEAD cipher with internal IV
8 generation, use the IV generator as a regular cipher. For example,
9 rfc4106(gcm(aes)) is the AEAD cipher with external IV generation and
11 the IV. Different IV generators are available.
Darchitecture.rst160 - givcipher for cipher with associated IV generator (see the geniv
161 entry below for the specification of the IV generator type used by
171 - ivsize: IV size in bytes
177 - geniv: IV generation type:
179 - eseqiv for encrypted sequence number based IV generation
181 - seqiv for sequence number based IV generation
185 - <builtin> is a marker that the cipher implements IV generation and
222 together with an IV generator (see geniv field in the /proc/crypto
223 listing for the known IV generators)
273 using the AEAD cipher with the automated IV generation. The shown
[all …]
Duserspace-if.rst159 should be processed for encryption or decryption. In addition, the IV is
174 - specification of the IV information marked with the flag ALG_SET_IV
218 should be processed for encryption or decryption. In addition, the IV is
233 - specification of the IV information marked with the flag ALG_SET_IV
Dapi-samples.rst71 /* IV will be random */
/Linux-v4.19/tools/perf/scripts/perl/Perf-Trace-Util/
DContext.c63 XSprePUSH; PUSHi((IV)RETVAL); in XS()
86 XSprePUSH; PUSHi((IV)RETVAL); in XS()
109 XSprePUSH; PUSHi((IV)RETVAL); in XS()
/Linux-v4.19/Documentation/device-mapper/
Ddm-crypt.txt14 Encryption cipher, encryption mode and Initial Vector (IV) generator.
24 format (selected by capi: prefix). The IV specification is the same
47 keys (for example IV seed) so the key contains more parts concatenated
71 The IV offset is a sector count that is added to the sector number
72 before creating the IV.
118 The <type> can be "none" if metadata is used only for persistent IV.
123 used for storing authentication tag (and persistent IV if needed).
131 IV generators will use sector number counted in <sector_size> units
134 For example, if <sector_size> is 4096 bytes, plain64 IV for the second
/Linux-v4.19/drivers/block/
Dcryptoloop.c110 int size, sector_t IV) in cryptoloop_transfer() argument
146 iv[0] = cpu_to_le32(IV & 0xffffffff); in cryptoloop_transfer()
156 IV++; in cryptoloop_transfer()
/Linux-v4.19/arch/x86/crypto/
Daesni-intel_asm.S148 #define IV %xmm3 macro
2521 movups (IVP), IV
2542 pxor IV, STATE1
2547 movaps IN4, IV
2550 movaps IN2, IV
2572 pxor IV, STATE
2574 movaps IN, IV
2581 movups IV, (IVP)
2614 movaps IV, CTR
2646 movaps CTR, IV
[all …]
/Linux-v4.19/arch/x86/crypto/sha512-mb/
Dsha512_mb_mgr_datastruct.S62 #FIELD _IV, 16, 8 # IV
81 # RES_DQ .IV, 1
/Linux-v4.19/arch/x86/crypto/sha1-mb/
Dsha1_mb_mgr_datastruct.S63 #FIELD _IV, 16, 8 # IV
82 # RES_DQ .IV, 1
/Linux-v4.19/arch/x86/crypto/sha256-mb/
Dsha256_mb_mgr_datastruct.S62 #FIELD _IV, 16, 8 # IV
81 # RES_DQ .IV, 1
/Linux-v4.19/drivers/crypto/chelsio/
Dchcr_algo.c74 #define IV AES_BLOCK_SIZE macro
778 chcr_req->sec_cpl.pldlen = htonl(IV + wrparam->bytes); in create_cipher_wr()
780 FILL_SEC_CPL_CIPHERSTOP_HI(0, 0, IV + 1, 0); in create_cipher_wr()
786 0, 0, IV >> 1); in create_cipher_wr()
818 temp = sizeof(struct cpl_rx_phys_dsgl) + dst_size + kctx_len + IV in create_cipher_wr()
1203 reqctx->imm = (transhdr_len + IV + req->nbytes) <= in process_cipher()
1205 bytes = IV + req->nbytes; in process_cipher()
1238 memcpy(reqctx->iv, req->info, IV); in process_cipher()
2208 reqctx->scratch_pad = reqctx->iv + IV; in chcr_aead_common_init()
2304 reqctx->imm = (transhdr_len + assoclen + IV + req->cryptlen) < in create_authenc_wr()
[all …]
/Linux-v4.19/drivers/zorro/
Dzorro.ids322 1500 Picasso IV Z2 RAM [Graphics Card]
323 1600 Picasso IV Z2 RAM [Graphics Card]
324 1700 Picasso IV Z2 [Graphics Card]
325 1800 Picasso IV Z3 [Graphics Card]
413 0100 AMax II/IV [Macintosh Emulator]
417 0600 Blizzard 1220-IV [Accelerator]
422 1100 Blizzard 1230-IV/1260 [Accelerator]
/Linux-v4.19/Documentation/hwmon/
Dw83627ehf111 * 5 "Smart Fan IV" mode
115 SmartFan IV mode is configurable only if it was configured at system
117 SmartFan IV operational parameters can not be configured at this time,
118 and the various pwm attributes are not used in SmartFan IV mode.
121 returned when reading pwm attributes is unrelated to SmartFan IV
Dnct6775108 * 5 "Smart Fan IV" mode
177 Smart Fan IV mode (5)
/Linux-v4.19/Documentation/media/uapi/mediactl/
Dmedia-controller.rst8 Part IV - Media Controller API
/Linux-v4.19/tools/perf/Documentation/
Dandroid.txt68 IV. Environment settings for running perf
75 IV. Run perf
/Linux-v4.19/net/batman-adv/
DKconfig40 of the currently used B.A.T.M.A.N. IV protocol. The main
46 compatible to B.A.T.M.A.N. IV networks.
/Linux-v4.19/Documentation/filesystems/
Dfscrypt.rst145 for contents encryption. Without per-file keys, to ensure IV
152 reused out of necessity. With a unique key per directory, IV reuse
218 the file is used as the IV. With the CBC mode of operation (not
219 recommended), ESSIV is used; specifically, the IV for CBC is the
225 filenames of up to 255 bytes, a constant initialization vector (IV) is
227 limits IV reuse to within a single directory. Note that IV reuse in
250 symlink also uses a unique key; hence, the hardcoded IV is not a
/Linux-v4.19/Documentation/i2c/busses/
Di2c-ali15x359 * "Aladdin IV" includes the M1541 Socket 7 North bridge
/Linux-v4.19/Documentation/rapidio/
Dmport_cdev.txt94 IV. Known problems
Dtsi721.txt74 IV. Version History
/Linux-v4.19/Documentation/networking/
Dudplite.txt86 A detailed discussion of UDP-Lite checksum coverage options is in section IV.
109 IV) KERNEL BEHAVIOUR WITH REGARD TO THE VARIOUS SOCKET OPTIONS
/Linux-v4.19/Documentation/powerpc/
Dqe_firmware.txt16 IV - Microcode Programming Details
57 IV - Microcode Programming Details
/Linux-v4.19/Documentation/ia64/
Defirtc.txt91 IV/ Wakeup Alarm service

12