This is what your quote about "AES-XTS prevents an attacker from changing one specific bit in a data unit" refers to. Here I write !^%@^^ to indicate that the previous 16-byte block will become gibberish once decrypted, and this gibberish will be beyond the attacker's …
AES_XTSEncrypt - Intel Developer Zone Sep 30, 2019 AES 256-bit XTS Military Grade Encryption and You - Krypterix Nov 29, 2015 Block Cipher Modes - Cryptographic Algorithm Validation The XTS-AES Validation System (XTSVS) specifies validation testing requirements for the XTS-AES mode in SP 800-38E. Testing Notes Prerequisites for XTS-AES testing are listed in the CAVP Frequently Asked Questions (CAVP FAQ) General Question GEN.5. Intel® AES-NI Performance Enhancements: HyTrust
encryption - For LUKS: The most preferable and safest
AES 192 is not supported in XTS mode. XTS (XEX-based tweaked-codebook mode with ciphertext stealing) is a mode of operation for the AES block cipher that is used for disk encryption. This mode does not require padding. Parameters: tweak (bytes-like) – The tweak is a 16 byte value typically derived from something like the disk sector number.
Dm-crypt full disk encryption - Gentoo Wiki
1762765 – RFE: hardware accelerated AES-XTS mode This will have a massive benefit for QEMU's LUKS implementation I/O performance since AES-XTS is the default mode though. Thus from QEMU's POV we'd like to explore options for getting this performance increase available in RHEL-8. Whether that's a backport to 1.8.3, or waiting & rebasing to 1.9.0 in some 8.x update doesn't matter to QEMU - we'd