From 95c2ed7c43c810439935cfdea98906cb3fda02bb Mon Sep 17 00:00:00 2001 From: ilia-kats Date: Sat, 1 Feb 2025 20:35:11 +0000 Subject: [PATCH] deploy: cb6edf1a5fed06ef7747eae26b2459953ef40ff7 --- pr/844/luks_device_module.html | 1 - pr/844/searchindex.js | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/pr/844/luks_device_module.html b/pr/844/luks_device_module.html index 96cf2b7c..0f3c08e7 100644 --- a/pr/844/luks_device_module.html +++ b/pr/844/luks_device_module.html @@ -362,7 +362,6 @@ see added in community.crypto 2.23.0

Determine how passphrases are provided to parameters such as passphrase, new_passphrase, and remove_passphrase.

-

Please note that binary passphrases cannot always contain all possible binary octets. When adding a new key to an existing container, a newline (0x0A) cannot be used since it indicates that the passphrase is over. If you want to use arbitrary binary data, you must use keyfiles.

Choices: