1. 14 Oct, 2018 1 commit
    • Milan Broz's avatar
      Wipe full header areas (including unused) during LUKS format. · c2bce3e9
      Milan Broz authored
      All previous version of cryptsetup wiped only first 4k for LUKS1
      and both JSON areas for LUKS2 (first 32k) and the allocated
      keyslot area (as it contained the generated key).
      Remaining areas (unused keyslots, padding, and alignment) were
      not wiped and could contain some previous data.
      Since this commit, the whole area up to the data offset is zeroed,
      and subsequently, all keyslots areas are wiped with random data.
      Only exceptions are
       - padding/alignment areas for detached header
         if the data offset is set to 0
       - bogus LUKS1 keyslot areas (upstream code never
         created such keyslots but someone could use that).
      This operation could slow down luksFormat on some devices, but
      it guarantees that after this operation LUKS header does not
      contain any foreign data.
  2. 10 Aug, 2018 1 commit
  3. 03 Aug, 2018 1 commit
    • Ondrej Kozina's avatar
      Calculate keyslots area size properly with detached headers. · ae8247fe
      Ondrej Kozina authored
      When LUKS2 crypt_format() is called with detached header and custom data
      alignment is requested, keyslots area is miscalculated. This mistake
      is correctly detected by LUKS2 validation code but it's feature
      regression with regard to LUKSv1 format.
  4. 26 Apr, 2018 1 commit
  5. 20 Jan, 2018 2 commits
  6. 23 Nov, 2017 1 commit
  7. 27 Sep, 2017 1 commit
  8. 24 Sep, 2017 1 commit