Lee Yarwood 97b085f448 luks: Explicitly use the luks1 type to ensure LUKS v1 is used ... I152fe10ff5a3131950b789d3fd4efa15c554ff09 attempted to ensure LUKS volumes were formatted using the LUKS v1 header format by using a type of `luks`. However from cryptsetup 2.1.0 (incorrectly referenced as 2.0.6 in the previous change) this type can actually refer to the newer LUKS v2 header format in environments where cryptsetup has not complied with the `--with-default-luks-format=LUKS1` build time configuration option [1]. This change now explicitly uses the luks1 type when formatting a device to ensure the correct LUKS v1 header format is used. [1] https://gitlab.com/cryptsetup/cryptsetup/blob/master/docs/v2.1.0-ReleaseNotes Closes-Bug: #1834851 Change-Id: I0010e9014c06a3a812d24d9d5ef598425ac5d5d4		2019-07-01 13:10:24 +01:00
..
__init__.py	encryptors: Delay removal of legacy provider names	2017-05-16 08:27:12 +00:00
base.py	Stop ignoring H405 hacking rule in tox	2017-05-24 00:44:57 +02:00
cryptsetup.py	Make close on cryptsetup volumes idempotent	2017-11-18 00:19:42 +00:00
luks.py	luks: Explicitly use the luks1 type to ensure LUKS v1 is used	2019-07-01 13:10:24 +01:00
nop.py	Add missing params in NoOpEncryptor	2019-01-22 14:23:43 +08:00